Re: Using streaming replication as log archiving

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Using streaming replication as log archiving
Date: 2010-10-01 11:01:50
Message-ID: AANLkTi=jgh+y+U_mPfDMJMB08MGrf=+_yhRYRXoX+s9M@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Oct 1, 2010 at 11:13, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
> On Wed, Sep 29, 2010 at 5:47 PM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
>> It's actually intentional. If we create a file at first, there is no
>> way to figure out exactly how far through a partial segment we are
>> without parsing the details of the log. This is useful both for the
>> admin (who can look at the directory and watch the file grow) and the
>> tool itself (to know when the .save file can be rotated away, when
>> recovering from a partial segment receive).
>>
>> My idea was to just have the admin pad the file when it's time to do
>> the restore. I could perhaps even add an option to the tool to do it -
>> the idea being it's a manual step still.
>>
>> Do you have another suggestion for how to provide those two things?
>
> My idea is to implement something like xlogdump in contrib and use it
> for those two things. Though it's harder to implement that than to do
> padding tool.

Yes, much harder. I prefer keeping the tool simple when possible ;)
Doesn't mean we couldn't do both, i guess.

> BTW, implementing something like xlogdump is already in TODO list:

Yes, obviously such a tool would be very useful independent of the
streaming thing.

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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2010-10-01 11:05:23 Re: recovery.conf location
Previous Message Fujii Masao 2010-10-01 11:01:40 Re: Standby registration