Skip site navigation (1) Skip section navigation (2)

BUG #7549: max_connections check should query master when starting standby

From: Chris Travers <chris(at)metatrontech(dot)com>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #7549: max_connections check should query master when starting standby
Date: 2012-09-18 08:49:18
Message-ID: CAPKNUtdmpkA2i3d6F=dmxzMVYHX_-m80=B+1-3C3+eCx0c36yQ@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-bugs
On Mon, Sep 17, 2012 at 11:46 PM, Craig Ringer <ringerc(at)ringerc(dot)id(dot)au>wrote:

> On 09/18/2012 07:57 AM, Fujii Masao wrote:
>
>> If you change the max_connections on the master, you need to take a
>> fresh backup from the master and start the standby from it.
>>
>
> WTF, really?
>
> What else breaks the replication and forces a re-clone?
>
> Another WTF from me too.

I can understand moving from read-only to read-write, but internally *why*
does this happen?  If it is the case, it needs to be clearly documented.

(mental note to test this and report back).

Why would this create a different timeline?

Best Wishes,
Chris Travers

In response to

pgsql-bugs by date

Next:From: Fujii MasaoDate: 2012-09-18 12:09:13
Subject: Re: BUG #7549: max_connections check should query master when starting standby
Previous:From: Heikki LinnakangasDate: 2012-09-18 06:48:31
Subject: Re: BUG #7549: max_connections check should query master when starting standby

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group