From: | Josh Berkus <josh(at)agliodbs(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Andres Freund <andres(at)2ndquadrant(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Gibheer <gibheer(at)zero-knowledge(dot)org>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Marko Tiikkaja <marko(at)joh(dot)to>, Mike Blackwell <maiku41(at)gmail(dot)com> |
Subject: | Re: Patch for reserved connections for replication users |
Date: | 2013-10-15 17:34:30 |
Message-ID: | 525D7CA6.1000901@agliodbs.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 10/15/2013 07:36 AM, Robert Haas wrote:
> On Tue, Oct 15, 2013 at 10:34 AM, Andres Freund <andres(at)2ndquadrant(dot)com> wrote:
>> Josh said we should treat replication connections in a separate "pool"
>> from normal database connections, right? So you withdraw your earlier
>> objection to that?
>
> I don't think that's what he said. Here's what I was referring to:
To clarify: I do, indeed, support the idea of treating replication
connections as a pool outside of max_connections. Here's why:
FATAL: connection limit exceeded for non-superusers
SHOW max_connections;
100
SELECT COUNT(*) FROM pg_stat_activity;
94
SHOW superuser_reserved_connections;
3
????
... search around quite a bit, eventually figure out that you have
three replication connections open. We've already set up an illogical
and hard-to-troubleshoot situation where replication connections do not
appear in pg_stat_activity, yet they are counted against max_connections.
You could argue that the same is true of superuser_reserved_connections,
but there's a couple reasons why it isn't:
1) if superusers are actually connected, that shows up in
pg_stat_activity (and given how many of our users run their apps as
superuser, they get to max_connections out anyway).
2) the error message spells out that there may be superuser connections
available.
--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2013-10-15 17:38:06 | Re: Auto-tuning work_mem and maintenance_work_mem |
Previous Message | Andres Freund | 2013-10-15 17:32:43 | Re: Auto-tuning work_mem and maintenance_work_mem |