| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
| Cc: | Magnus Hagander <magnus(at)hagander(dot)net>, 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 11:19:04 |
| Message-ID: | 4EA93E28.1000004@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 27.10.2011 14:09, Fujii Masao wrote:
> On Thu, Oct 27, 2011 at 7:48 PM, Magnus Hagander<magnus(at)hagander(dot)net> wrote:
>> I'm rewriting the handling of partial files per the other thread
>> started by Heikki. The idea is that there will be an actual .partial
>> file in there when pg_receivexlog has ended, and you have to deal with
>> it manually. The typical way would be to pad it with zeroes to the
>> end. Doing such padding would solve this recovery issue, correct?
>
> Yes. But that sounds unuserfriendly. Padding the WAL file manually
> is easy-to-do for a user?
"truncate -s 16M <file>" works at least on my Linux system. Not sure how
you'd do it on Windows.
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..
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2011-10-27 11:23:24 | Re: Updated version of pg_receivexlog |
| Previous Message | Fujii Masao | 2011-10-27 11:09:27 | Re: Updated version of pg_receivexlog |