Re: Updated version of pg_receivexlog - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Updated version of pg_receivexlog
Date
Msg-id 28587.1319727240@sss.pgh.pa.us
Whole thread Raw
In response to Re: Updated version of pg_receivexlog  (Magnus Hagander <magnus@hagander.net>)
Responses Re: Updated version of pg_receivexlog  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers
Magnus Hagander <magnus@hagander.net> writes:
> On Thu, Oct 27, 2011 at 13:19, Heikki Linnakangas
> <heikki.linnakangas@enterprisedb.com> wrote:
>> On 27.10.2011 14:09, Fujii Masao wrote:
>>> Yes. But that sounds unuserfriendly. Padding the WAL file manually
>>> is easy-to-do for a user?

> I'd definitely want to avoid anything that requires pg_receivexlog to
> actually *parse* the WAL. That'll make it way more complex than I'd
> like.

What parsing?  Just pad to 16MB with zeroes.  In fact, I think the
receiver should just create the file that size to start with, and then
write received data into it, much like normal WAL creation does.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Hot Backup with rsync fails at pg_clog if under load
Next
From: Magnus Hagander
Date:
Subject: Re: Updated version of pg_receivexlog