From: | Alex Good <alexjsgood(at)gmail(dot)com> |
---|---|
To: | Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Recovery continually requests new WAL files |
Date: | 2012-06-13 08:29:26 |
Message-ID: | 4FD84F66.50402@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 13/06/12 09:10, Albe Laurenz wrote:
> Alex Good wrote:
>> I have a simple setup with one master and one backup server. I have an
>> issue where I have performed a backup and copied it to the data
>> directory for the slave, written a recovery.conf and copied in the
>> backup_label file and then started the server, it happily restores
>> everything up until and including the WAL file mentioned in the
>> backup_label and then attempts to obtain the next archive file which
> has
>> not yet been archived. I can't for the life of me figure out what is
>> going on.
> What else would you expect?
>
> Are you planning to use streaming replication?
>
> If yes, what are your configuration parameters for replication?
>
> Yours,
> Laurenz Albe
What I expected to see was the server requesting each WAL file up until
the one which was archived during pg_stop_backup and then the server
would consider itself to be recovered. Clearly I have misunderstood
something here.
These two servers are actually sat behind pgpool which is in replication
mode (so I don't have streaming replication set up) which I chose
beccause it gives me synchronous replication as well as automatic
failover. I am trying to understand the recovery process so I can use it
to set up pgpools' online recovery feature.
Thanks
Alex Good
Alex
From | Date | Subject | |
---|---|---|---|
Next Message | Albe Laurenz | 2012-06-13 09:29:18 | Re: Recovery continually requests new WAL files |
Previous Message | Pavel Stehule | 2012-06-13 08:22:27 | Re: PostgreSQL 9.2, SQL functions' named vs numbered parameters. |