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

Re: [HACKERS] Streaming replication document improvements

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Josh Berkus <josh(at)agliodbs(dot)com>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, pgsql-docs(at)postgresql(dot)org, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [HACKERS] Streaming replication document improvements
Date: 2010-04-21 01:40:09
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-docspgsql-hackers
On Tue, Apr 20, 2010 at 11:01 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>> 3. Your proposal
>>    Treat superuser replication connection like non-superuser one
> Well, only for this one very specific purpose.  I would adjust the
> docs like this:
> Determines the number of connection "slots" that are reserved for
> connections by PostgreSQL  superusers. At most max_connections
> connections can ever be active simultaneously. Whenever the number of
> active concurrent connections is at least max_connections minus
> superuser_reserved_connections, new connections will be accepted only
> for superusers, and no new replication connections will be accepted.
> I think that's pretty simple and clear.

Yeah, I'm sold.


Fujii Masao
NTT Open Source Software Center

In response to

pgsql-docs by date

Next:From: Robert HaasDate: 2010-04-21 16:10:10
Subject: Re: [HACKERS] Streaming replication document improvements
Previous:From: Tom LaneDate: 2010-04-20 23:53:36
Subject: Re: [HACKERS] Streaming replication document improvements

pgsql-hackers by date

Next:From: Takahiro ItagakiDate: 2010-04-21 01:50:26
Subject: Re: [GENERAL] trouble with to_char('L')
Previous:From: Tom LaneDate: 2010-04-21 01:13:09
Subject: Re: Vacuum cancels autovacuum error message confusing?

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