Skip site navigation (1) Skip section navigation (2)

Re: don't allow walsender to consume superuser_reserved_connection slots, or during shutdown

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: don't allow walsender to consume superuser_reserved_connection slots, or during shutdown
Date: 2010-04-22 13:23:40
Message-ID: t2k603c8f071004220623s47860c70o659050e32810a9f0@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
On Wed, Apr 21, 2010 at 10:01 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> Here's the fine patch.  The actual code changes are simple and seem to
>> work as expected, but I struggled a bit with the phrasing of the
>> messages.  Feel free to suggest improvements.
>
> Stick with the original wording?  I don't really see a need to change it.

I don't think that's a good idea.  If we just say that the remaining
connection slots are for superusers, someone will inevitably ask us
why their superuser replication can't connect.  I think it's important
to phrase things as accurately as possible.

...Robert

In response to

pgsql-hackers by date

Next:From: Robert HaasDate: 2010-04-22 15:10:34
Subject: Re: Thread safety and libxml2
Previous:From: Simon RiggsDate: 2010-04-22 09:31:58
Subject: Re: Hot Standby b-tree delete records review

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group