From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Jeremy Finzel <finzelj(at)gmail(dot)com>, PostgreSQL General <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Do all superuser processes count toward superuser_reserved_connections? |
Date: | 2019-03-15 14:48:27 |
Message-ID: | 1bb28189-8ba2-0666-f1e9-bec48691129c@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 3/14/19 8:23 AM, Jeremy Finzel wrote:
> I don't find a clear mention in the docs of superuser processes that are
> exempt from counting toward superuser_reserved_connections. So I would
> think that it's possible that postgres autovac workers ought to count
> toward that. Am I wrong about that? I actually have the same question
AFAICK autovacuum workers do not use the connections referred to above.
The details can be found here:
https://doxygen.postgresql.org/autovacuum_8c.html
> about pglogical replication background workers and manager, which also
> run as postgres.
But the actual connection can be by a different user:
https://www.postgresql.org/docs/11/logical-replication-security.html
>
> Do I need to increase my limit to account for these workers, or are some
> or all of these processes ignored by superuser_reserved_connections?
I am still learning about logical replication, but as I understand it
the process uses replication slots:
So configuring for that involves:
https://www.postgresql.org/docs/11/logical-replication-config.html
From the looks of it superuser_reserved_connections is not impacted.
>
> Many thanks!
> Jeremy
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Jeremy Finzel | 2019-03-15 15:16:27 | Re: Do all superuser processes count toward superuser_reserved_connections? |
Previous Message | Wim Bertels | 2019-03-15 09:12:40 | Re: Camel case identifiers and folding |