Re: postgres standby won't start - Mailing list pgsql-general

Ok, I did the pg_basebackup successfully and sent the file (.tar) to the target and expanded it over the data
directory.Looks like I am still out of sync when trying to open the DB(or start it). 

2015-10-07 16:04:13 EDT FATAL:  timeline 26 of the primary does not match recovery target timeline 22

Any ideas?



Thanks
Kumar Ramalingam
X6015288


-----Original Message-----
From: Adrian Klaver [mailto:adrian.klaver@aklaver.com]
Sent: Wednesday, October 07, 2015 1:25 PM
To: Ramalingam, Sankarakumar; pgsql-general@postgresql.org
Subject: Re: [GENERAL] postgres standby won't start

On 10/07/2015 10:02 AM, Ramalingam, Sankarakumar wrote:
> Hi Adrian,
> Thanks for your prompt response. I used pg_basebackup to backup my source server. I am starting this exercise on our
QAside so I can do a dry run before hitting production. Would I be able to restore that backup on my target standby? If
yes,would you guide me to the steps. Thanks a lot for your invaluable suggestions overall to this forum. 

The steps can be found here:

http://www.postgresql.org/docs/9.4/interactive/app-pgbasebackup.html

Look at the examples at the bottom and substitute the data directory for the standby in the -D portion. Important:

-D directory
--pgdata=directory

     Directory to write the output to. pg_basebackup will create the directory and any parent directories if necessary.
Thedirectory may already exist, but it is an error if the directory already exists and is not empty. 

To be on safe side you could move the current files in the standby directory to another location before pointing
pg_basebackupat it. 

>
>
>
> Thanks
> Kumar Ramalingam
> X6015288
>
>
> -----Original Message-----
> From: Adrian Klaver [mailto:adrian.klaver@aklaver.com]
> Sent: Monday, October 05, 2015 7:35 PM
> To: Ramalingam, Sankarakumar; pgsql-general@postgresql.org
> Subject: Re: [GENERAL] postgres standby won't start
>
> On 10/05/2015 12:35 PM, Ramalingam, Sankarakumar wrote:
>> Thanks Adrian.
>>
>> My primary is doing  fine. Only the standby. I am noticing it after a while..my Bad!!
>> Primary setting
>> #--------------------------------------------------------------------
>> -
>> ---------
>> # REPLICATION
>> #--------------------------------------------------------------------
>> -
>> ---------
>>
>> max_wal_senders = 5
>> wal_sender_delay = 1s
>> wal_keep_segments = 512
>> vacuum_defer_cleanup_age = 20
>> hot_standby = on
>>
>> Since I am unable to bring standby up, would the pg_basebackup help me out here for a complete sync? Thanks again.
>
> The problem is that the WAL files got recycled on the primary and are no longer available there, which is why the
standbyis failing. If you where archiving the WAL files somewhere, you could fetch the missing WAL files from there. If
thatis not the case then you will need to rebuild the standby to the current state(more or less) of the primary. The
simplestway is to use pg_backup, but that means starting with either no data directory or an empty one on the standby.
Thedocs page steps you through the procedure. 
>
>>
>>
>>
>> Thanks
>> Kumar Ramalingam
>> X6015288
>>
>>
>
>
>
> --
> Adrian Klaver
> adrian.klaver@aklaver.com
> The information contained in this e-mail and in any attachments is intended only for the person or entity to which it
isaddressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other
useof, or taking of any action in reliance upon, this information by persons or entities other than the intended
recipientis prohibited. This message has been scanned for known computer viruses. 
>


--
Adrian Klaver
adrian.klaver@aklaver.com
The information contained in this e-mail and in any attachments is intended only for the person or entity to which it
isaddressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other
useof, or taking of any action in reliance upon, this information by persons or entities other than the intended
recipientis prohibited. This message has been scanned for known computer viruses.