Re: Hot Standby, max_connections and max_prepared_transactions

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Simon Riggs <simon(at)2ndQuadrant(dot)com>
Cc: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Hot Standby, max_connections and max_prepared_transactions
Date: 2009-09-04 05:25:07
Message-ID: 7993.1252041907@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Simon Riggs <simon(at)2ndQuadrant(dot)com> writes:
> 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.

Just to be clear: you're proposing requiring that these be set the
same on master and slave? I don't have a problem with that, but
I do suggest that we must provide a mechanism to check it --- I don't
want DBAs to be faced with obscure failures when (not if) they
mess it up. Perhaps include the values in checkpoint WAL records?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Simon Riggs 2009-09-04 06:29:52 Re: Hot Standby, max_connections and max_prepared_transactions
Previous Message Hitoshi Harada 2009-09-04 03:19:44 Re: Implementation of GROUPING SETS (T431: Extended grouping capabilities)