Re: Updated version of pg_receivexlog

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Cc: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(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 07:49:35
Message-ID: CABUevEyLYWTscvs4-wVvQ86p893vEJ5=buHMYhf9tsJKAbK4dA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Oct 27, 2011 at 09:46, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
> On Thu, Oct 27, 2011 at 4:40 PM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
>> On Thu, Oct 27, 2011 at 09:29, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
>>> On Thu, Oct 27, 2011 at 3:29 AM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
>>>> I've applied this version with a few more minor changes that Heikki found.
>>>
>>> Cool!
>>>
>>> When I tried pg_receivexlog and checked the contents of streamed WAL file by
>>> xlogdump, I found that recent WAL records that walsender has already sent don't
>>> exist in that WAL file. I expected that pg_receivexlog writes the streamed WAL
>>> records to the disk as soon as possible, but it doesn't. Is this
>>> intentional? Or bug?
>>> Am I missing something?
>>
>> It writes it to disk as soon as possible, but doesn't fsync() until
>> the end of each segment. Are you by any chance looking at the file
>> while it's running?
>
> No. I looked at that file after shutting down the master server.

Ugh, in that case something is certainly wrong. There is nothing but
setting up some offset values between PQgetCopyData() and write()...

--
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2011-10-27 08:12:26 Re: Updated version of pg_receivexlog
Previous Message Fujii Masao 2011-10-27 07:46:50 Re: Updated version of pg_receivexlog