Re: warm standby with WAL shipping

From: Geoffrey <lists(at)serioustechnology(dot)com>
To: jd(at)commandprompt(dot)com
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: warm standby with WAL shipping
Date: 2009-06-02 20:51:47
Message-ID: 4A2590E3.2090303@serioustechnology.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Joshua D. Drake wrote:
> On Tue, 2009-06-02 at 15:21 -0400, Geoffrey wrote:
>
>> My problem is, I never see a *.history file, thus my script sits in a
>> loop looking for it. I see the WAL files showing up on the archive
>> server, but I don't see a *.history file.
>>
>> What am I missing?
>
> pg_standby it self isn't a solution for warm standby. It is a component
> thereof. Also don't use SCP. Use rsync. Take a look at walmgr or
> PITRTools it will make your life easier.

So, I'm looking at the PITRTools stuff, but I really want to understand
how this all works. I'm shipping my wall files fine. I've been able to
recreate my database from a backup and the accumulated WAL files. The
problem with my current process is as noted, my script keeps looking for
the *.history file, but never sees it. I see the list of files on my
archive machine growing, so I know WAL shipping is working. I've created
my backup as instructed in the docs. I don't know how/where the
*.history file is generated and/or why it's not showing up in the
archive directory with the WAL files.

--
Until later, Geoffrey

Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety.
- Benjamin Franklin

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Martijn van Oosterhout 2009-06-02 21:01:27 Re: Really out of memory?
Previous Message Tom Lane 2009-06-02 20:45:57 Re: Really out of memory?