From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Melvin Davidson <melvin6925(at)gmail(dot)com>, "Edson F(dot) Lidorio" <edson(at)openmailbox(dot)org> |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Standby problem after restore_command Implementation |
Date: | 2015-05-05 22:09:47 |
Message-ID: | 55493FAB.90007@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 05/05/2015 11:21 AM, Melvin Davidson wrote:
> Have you allowed access to user "replication" in the master pg_hba.conf
> and done a
> SELECT pg_reload_conf()?
>
> Can you ping the master from the standby?
>
> Did you RTFM?
> http://www.postgresql.org/docs/9.2/interactive/warm-standby.html
>
> 25.2.3 Preparing the Master for Standby Servers
> 25.2.4 Setting Up a Standby Server
See the OPs original post:
http://www.postgresql.org/message-id/5546C3DC.5070808@openmailbox.org
The OP had streaming only replication working, so the basics are there.
The wheels fell off when WAL archiving was introduced. Best guess is
this is a timing issue, the relevant WALs got recycled while archiving
was being set up and the standby was down.
>
>
>
> On Tue, May 5, 2015 at 2:05 PM, Edson F. Lidorio <edson(at)openmailbox(dot)org
> <mailto:edson(at)openmailbox(dot)org>> wrote:
>
> __
>
> Em 2015-05-05 14:31, Adrian Klaver escreveu:
>
>> On 05/05/2015 08:35 AM, Edson F. Lidorio wrote:
>>> On 05-05-2015 11:22, Melvin Davidson wrote:
>>>> It's possible you have wal_keep_segments set too low. What
>>>> happens is that the master will keep the wals ( in your case 20)
>>>> after processing them, before sending them off to the great
>>>> black hole in the network (deleting) and making them unavailable
>>>> to the standby. Try increasing wal_keep_segments = 100.
>>> Increased thewal_keep_segments=100andkeeps popping upthe same
>>> message:
>> The message did not come through. Also increasing wal_keep_segments only works for the future, it will not deal with a WAL file that has already been recycled before the setting was changed.
>>> A question thatI have! astheslave servercan seethis folderin
>>> themaster? /mnt/server/archivedir/
>> So have you tried logging into the standby and then accessing the directory on the master manually. In other words copy a file from the master to standby using cp from the standby command line.
>>> Sorrymy doubtsI'mbasicbeginner!
>> --
>> Adrian Klaver
>> adrian(dot)klaver(at)aklaver(dot)com <mailto:adrian(dot)klaver(at)aklaver(dot)com>
>>
> OK,I'm going to dothis testtoo.
>
> --
> Edson F. Lidorio
>
> Atenção: Este e-mail pode conter anexos no formato ODF (Open Document
> Format)/ABNT (extensões odt, ods, odp, odb, odg). Antes de pedir os anexos
> em outro formato, você pode instalar gratuita e livremente o LibreOffice (
> http://pt-br.libreoffice.org/)
>
>
>
>
> --
> *Melvin Davidson*
> I reserve the right to fantasize. Whether or not you
> wish to share my fantasy is entirely up to you.
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Venkata Balaji N | 2015-05-05 22:49:22 | Re: Standby problem after restore_command Implementation |
Previous Message | Melvin Davidson | 2015-05-05 21:42:56 | Re: documenting tables version control |