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

From Dimitri Fontaine
Subject Re: Updated version of pg_receivexlog
Date
Msg-id m2ehxyzcu1.fsf@2ndQuadrant.fr
Whole thread Raw
In response to 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:
>> Perhaps we should add automatic padding in the server, though. It wouldn't
>> take much code in the server, and would make life easier for people writing
>> their scripts. Maybe even have the backend check for a .partial file if it
>> can't find a regularly named XLOG file. Needs some thought..
>
> 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 about creating the WAL file filled up with zeroes at the receiving
end and then overwriting data as we receive it?

Regards,
-- 
Dimitri Fontaine
http://2ndQuadrant.fr     PostgreSQL : Expertise, Formation et Support


pgsql-hackers by date:

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