Re: Using streaming replication as log archiving - Mailing list pgsql-hackers

From Fujii Masao
Subject Re: Using streaming replication as log archiving
Date
Msg-id AANLkTikz4LxtYtn7PGUBPHBNMrJChe6y+axzQWP7Jumb@mail.gmail.com
Whole thread Raw
In response to Re: Using streaming replication as log archiving  (Magnus Hagander <magnus@hagander.net>)
Responses Re: Using streaming replication as log archiving
List pgsql-hackers
On Tue, Sep 28, 2010 at 5:23 PM, Magnus Hagander <magnus@hagander.net> wrote:
>> When I ran that, the size of the WAL file in inprogress directory
>> became more than 16MB. Obviously something isn't right.
>
> Wow, that's weird. I'm unable to reproduce that here - can you try to
> figure out why that happened?

Sorry, I overlooked the single-digit figure in the result of "ls -l".
To be exact, the size of the WAL file in inprogress directory can be
less than 16MB. Here is the result of "ls -l inprogress".

$ ls -l inprogress/
total 1724
-rw-rw-r-- 1 postgres postgres 1757352 Sep 29 12:03 000000010000000000000003

This also would be problem since the WAL file smaller than 16MB cannot
be used for recovery. I think that pg_streamrecv should create 16MB
file with zero at first, and write the received WAL records in that, as
walreceiver does.

Regards,

-- 
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Path question
Next
From: Josh Kupershmidt
Date:
Subject: Re: I: About "Our CLUSTER implementation is pessimal" patch