From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Louis Battuello <louis(dot)battuello(at)etasseo(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: Standby pg_dump Conflict with Recovery |
Date: | 2015-10-16 13:35:17 |
Message-ID: | 5620FD15.60302@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 10/15/2015 03:30 PM, Louis Battuello wrote:
>
>> On Oct 15, 2015, at 6:16 PM, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com
>> <mailto:adrian(dot)klaver(at)aklaver(dot)com>> wrote:
>>
>>
>> How did you set and temporarily enable the settings
>
> I changed the settings in the postgresql.conf file, restarted the
> standby server, checked that there wasn't any activity on the primary or
> the standby, and ran the pg_dump on the standby again - which failed. I
> watched the xmin value on the primary pg_replication_slots, which held
> steady until the dump failed.
>
> Then, I changed the delay settings back to the defaults and restarted
> the standby so I wouldn’t affect the replication during the next
> business day.
>
Hmm. From what I see it looks okay.
Have looked in the logs of the master to see what is going on around the
time the query is cancelled?
Also in the standby logs before and after the ERROR?
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Louis Battuello | 2015-10-16 14:50:41 | Re: Standby pg_dump Conflict with Recovery |
Previous Message | Albe Laurenz | 2015-10-16 12:23:10 | Re: pgpool ssl handshake failure |