Re: Forcing wal rotation - Mailing list pgsql-hackers

From Martijn van Oosterhout
Subject Re: Forcing wal rotation
Date
Msg-id 20060714154541.GG551@svana.org
Whole thread Raw
In response to Re: Forcing wal rotation  ("Florian G. Pflug" <fgp@phlo.org>)
Responses Re: Forcing wal rotation  ("Florian G. Pflug" <fgp@phlo.org>)
List 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@svana.org>   http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.

pgsql-hackers by date:

Previous
From: "Florian G. Pflug"
Date:
Subject: Re: Forcing wal rotation
Next
From: "Florian G. Pflug"
Date:
Subject: Re: Forcing wal rotation