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

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>
Cc: Craig Ringer <ringerc(at)ringerc(dot)id(dot)au>, petsku(at)petteriraty(dot)eu, pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #7549: max_connections check should query master when starting standby
Date: 2012-09-18 12:09:13
Message-ID: CAHGQGwGw1BTuNa+F3m1CXtcVP3Gr2Mved+rC4Q+c0pMG2npAsw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, Sep 18, 2012 at 3:48 PM, Heikki Linnakangas
<hlinnakangas(at)vmware(dot)com> wrote:
> On 18.09.2012 09:46, Craig Ringer 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?
>
>
> No. It's enough to bump up max_connections on the standby, and restart.

Hmm... Petteri wants to solve the issue without changing anything
on the standby, according to his original post. So in his case, a fresh
backup is required.

Of course my previous answer was confusing...

Regards,

--
Fujii Masao

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message kamalnitya87 2012-09-18 12:26:27 BUG #7554: save image into database using jsp and servlet
Previous Message Chris Travers 2012-09-18 08:49:18 BUG #7549: max_connections check should query master when starting standby