From: | Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Jaime Casanova <jaime(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Updated version of pg_receivexlog |
Date: | 2011-10-27 15:14:14 |
Message-ID: | m2ehxyzcu1.fsf@2ndQuadrant.fr |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Magnus Hagander <magnus(at)hagander(dot)net> writes:
> On Thu, Oct 27, 2011 at 13:19, Heikki Linnakangas
> <heikki(dot)linnakangas(at)enterprisedb(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2011-10-27 15:25:25 | Re: Hot Backup with rsync fails at pg_clog if under load |
Previous Message | Magnus Hagander | 2011-10-27 14:57:22 | Re: Updated version of pg_receivexlog |