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

From Heikki Linnakangas
Subject Re: Hot Standby, max_connections and max_prepared_transactions
Date
Msg-id 4AA01776.8050105@enterprisedb.com
Whole thread Raw
In response to Hot Standby, max_connections and max_prepared_transactions  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: Hot Standby, max_connections and max_prepared_transactions
List pgsql-hackers
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.

--  Heikki Linnakangas EnterpriseDB   http://www.enterprisedb.com


pgsql-hackers by date:

Previous
From: gabrielle
Date:
Subject: Re: Commitfest Code Sprint with PUGs
Next
From: Webb Sprague
Date:
Subject: Re: Commitfest Code Sprint with PUGs