Re: replication_reserved_connections
От | Andres Freund |
---|---|
Тема | Re: replication_reserved_connections |
Дата | |
Msg-id | 20130728185016.GA10876@alap2.anarazel.de обсуждение исходный текст |
Ответ на | replication_reserved_connections (Marko Tiikkaja <marko@joh.to>) |
Ответы |
Re: replication_reserved_connections
|
Список | 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
В списке pgsql-hackers по дате отправления: