Re: Hot Standby, max_connections and max_prepared_transactions - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Hot Standby, max_connections and max_prepared_transactions
Date
Msg-id 603c8f070909040626q271c8106h127d28ccf9573ce6@mail.gmail.com
Whole thread Raw
In response to Re: Hot Standby, max_connections and max_prepared_transactions  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: Hot Standby, max_connections and max_prepared_transactions
Re: Hot Standby, max_connections and max_prepared_transactions
List pgsql-hackers
On Thu, Sep 3, 2009 at 5:50 PM, Simon Riggs<simon@2ndquadrant.com> wrote:
>
> On Thu, 2009-09-03 at 22:22 +0300, Heikki Linnakangas wrote:
>> Simon Riggs wrote:
>> > I propose we just accept that both max_connections and
>> > max_prepared_transactions need to be set correctly for recovery to work.
>> > This will make the state transitions more robust and it will avoid
>> > spurious and hard to test error messages.
>> >
>> > Any objections to me removing this slice of code from the patch?
>>
>> Umm, what slice of code? I don't recall any code trying to make it work.
>
> Well, its there. Perhaps the full functionality has been clipped in
> recent changes, but there are still unwanted ramifications in the design
> that I think would be best to remove. No loss of functionality, just HS
> won't activate unless max_connections is set >= value on primary.

I'm not sure if you're referring to the work that I did, but if so
it's not nearly that significant.  I haven't done anything much beyond
some code cleanup.  Hopefully you're planning to keep that part, as it
would be a shame if I had done it for nothing.  Can't wait to see the
revised patch.

...Robert


pgsql-hackers by date:

Previous
From: Oleg Bartunov
Date:
Subject: PgCon 2009 Developer Meeting pictures
Next
From: Simon Riggs
Date:
Subject: Re: Hot Standby, max_connections and max_prepared_transactions