| From: | Martijn van Oosterhout <kleptog(at)svana(dot)org> |
|---|---|
| To: | "Florian G(dot) Pflug" <fgp(at)phlo(dot)org> |
| Cc: | Postgresql-General <pgsql-hackers(at)postgresql(dot)org>, "A(dot)M(dot)" <agentm(at)themactionfaction(dot)com> |
| Subject: | Re: Forcing wal rotation |
| Date: | 2006-07-14 15:45:41 |
| Message-ID: | 20060714154541.GG551@svana.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Jul 14, 2006 at 05:36:58PM +0200, Florian G. Pflug wrote:
> That was the idea - providing pg_rotate_wal(), which would guarantee that
> the wal is rotatted at least once if called. Thinking further about this,
> for a first prove of concept, I'd be enough to write a C function
> pg_current_walsegment(). pg_rotate_wal() could then be a plpgsql function,
> that e.g. creates a temporary table, and fills it with data, until the
> return value of pg_current_walsegment() changes.
Temporary tables don't get xlogged. It would probably be easier to hook
into the xlog machinery and create NOP records, like you originally
suggested.
Have a nice day,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Florian G. Pflug | 2006-07-14 15:57:50 | Re: Forcing wal rotation |
| Previous Message | Florian G. Pflug | 2006-07-14 15:36:58 | Re: Forcing wal rotation |