Update docs and error message for superuser_reserved_connections.
authorRobert Haas <[email protected]>
Fri, 20 Jan 2023 20:23:04 +0000 (15:23 -0500)
committerRobert Haas <[email protected]>
Fri, 20 Jan 2023 20:23:04 +0000 (15:23 -0500)
Commit ea92368cd1da1e290f9ab8efb7f60cb7598fc310 made max_wal_senders
a separate pool of backends from max_connections, but the documentation
and error message for superuser_reserved_connections weren't updated
at the time, and as a result are somewhat misleading. Update.

This is arguably a back-patchable bug fix, but because it seems quite
minor, no back-patch.

Patch by Nathan Bossart. Reviewed by Tushar Ahuja and by me.

Discussion: http://postgr.es/m/20230119194601.GA4105788@nathanxps13

doc/src/sgml/config.sgml
src/backend/utils/init/postinit.c

index 89d53f2a6458a78fef54bf4e06216699a79e149f..e019a1aac9937dbf9c7053d71c98d70c5d553825 100644 (file)
@@ -725,8 +725,7 @@ include_dir 'conf.d'
         number of active concurrent connections is at least
         <varname>max_connections</varname> minus
         <varname>superuser_reserved_connections</varname>, new
-        connections will be accepted only for superusers, and no
-        new replication connections will be accepted.
+        connections will be accepted only for superusers.
        </para>
 
        <para>
index ae5a85ed65be5fe61cc37fc219412769546a86d8..9145d96b385c7ec1fa8f1520933e503ee03b614c 100644 (file)
@@ -931,7 +931,7 @@ InitPostgres(const char *in_dbname, Oid dboid,
        !HaveNFreeProcs(ReservedBackends))
        ereport(FATAL,
                (errcode(ERRCODE_TOO_MANY_CONNECTIONS),
-                errmsg("remaining connection slots are reserved for non-replication superuser connections")));
+                errmsg("remaining connection slots are reserved for superusers")));
 
    /* Check replication permissions needed for walsender processes. */
    if (am_walsender)