From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
---|---|
To: | Marko Tiikkaja <marko(at)joh(dot)to> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: replication_reserved_connections |
Date: | 2013-07-28 18:50:16 |
Message-ID: | 20130728185016.GA10876@alap2.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2013-07-28 02:23:47 +0200, Marko Tiikkaja wrote:
> While you could limit the number of connections for non-replication roles,
> that's not always possible or desirable. I would like to introduce a way to
> reserve connection slots for replication. However, it's not clear how this
> would work. I looked at how superuser_reserved_connections is implented,
> and with small changes I could see how to implement two ideas:
>
> Does anyone see a better way to do this? I'm not too satisfied with either
> of these ideas.
Personally I think we should just shouldn't allow normal connections for
the backend slots added by max_wal_senders. They are internally *added*
to max_connections, so limiting that seems perfectly fine to me since
the system provides max_connections connections externally.
Hm... I wonder how that's managed for 9.4's max_worker_processes.
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2013-07-28 19:37:49 | Re: install libpq.dll in bin directory on Windows / Cygwin |
Previous Message | Tom Lane | 2013-07-28 18:43:50 | Re: Review: UNNEST (and other functions) WITH ORDINALITY |