Re: Forcing wal rotation

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "Florian G(dot) Pflug" <fgp(at)phlo(dot)org>, "Postgresql-General" <pgsql-hackers(at)postgresql(dot)org>
Cc: "A(dot)M(dot)" <agentm(at)themactionfaction(dot)com>
Subject: Re: Forcing wal rotation
Date: 2006-07-14 16:17:25
Message-ID: E7F85A1B5FF8D44C8A1AF6885BC9A0E40154BF83@ratbert.vale-housing.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> -----Original Message-----
> From: pgsql-hackers-owner(at)postgresql(dot)org
> [mailto:pgsql-hackers-owner(at)postgresql(dot)org] On Behalf Of
> Florian G. Pflug
> Sent: 14 July 2006 16:37
> To: Postgresql-General
> Cc: A.M.
> Subject: Re: [HACKERS] Forcing wal rotation
>
> > How about an SQL-level function that calls the wal scripts?
> This would
> > also allow "important" transactions to push data to the
> standy server
> > regardless of the wal size.
> 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.

You might wanna speak to Simon Riggs before starting anything - he was
planning to work on this (log rotation) at the Code Sprint. Don't know
if he actually got to it though.

Regards, Dave.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2006-07-14 16:20:34 Re: contrib promotion?
Previous Message Tom Lane 2006-07-14 16:09:31 Re: Forcing wal rotation