Re: Bugs in superuser_reserved_connections and max_wal_senders vs max_connections - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Bugs in superuser_reserved_connections and max_wal_senders vs max_connections
Date
Msg-id 955.1344521840@sss.pgh.pa.us
Whole thread Raw
In response to Bugs in superuser_reserved_connections and max_wal_senders vs max_connections  (Magnus Hagander <magnus@hagander.net>)
Responses Re: Bugs in superuser_reserved_connections and max_wal_senders vs max_connections
List pgsql-hackers
Magnus Hagander <magnus@hagander.net> writes:
> The check in PostmasterMain():
>     if (ReservedBackends >= MaxBackends)
>     {
>         write_stderr("%s: superuser_reserved_connections must be less than
> max_connections\n", progname);
>         ExitPostmaster(1);
>     }

> should probably check against MaxConnections instead of MaxBackends, I think?

Yeah, this code probably dates from before there was a difference.

In general, I'd bet that this is not the only place where the wrong one
of those variables is being consulted.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Inserting heap tuples in bulk in COPY
Next
From: "Kevin Grittner"
Date:
Subject: Wiki link for max_connections? (Fwd: Re: [ADMIN] PostgreSQL oom_adj postmaster process to -17)