Re: BUG #7549: max_connections check should query master when starting standby - Mailing list pgsql-bugs

From Bruce Momjian
Subject Re: BUG #7549: max_connections check should query master when starting standby
Date
Msg-id 20120926160404.GD11785@momjian.us
Whole thread Raw
In response to Re: BUG #7549: max_connections check should query master when starting standby  (Fujii Masao <masao.fujii@gmail.com>)
List pgsql-bugs
On Tue, Sep 18, 2012 at 09:09:13PM +0900, Fujii Masao wrote:
> On Tue, Sep 18, 2012 at 3:48 PM, Heikki Linnakangas
> <hlinnakangas@vmware.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...

I assume you mean the slave needs an updated copy of the master's
config file changes, not an entire copy of the data directory.

--
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + It's impossible for everything to be true. +

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: [DOCS] BUG #7543: Invalid table alias: DELETE FROM table *
Next
From: PETIT Raphael
Date:
Subject: Re: BUG #7564: window installer of Postgresql 9.2 and service configuration