Re: Bugs in superuser_reserved_connections and max_wal_senders vs max_connections

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Bugs in superuser_reserved_connections and max_wal_senders vs max_connections
Date: 2012-08-09 14:17:20
Message-ID: 955.1344521840@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Magnus Hagander <magnus(at)hagander(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kevin Grittner 2012-08-09 14:22:38 Wiki link for max_connections? (Fwd: Re: PostgreSQL oom_adj postmaster process to -17)
Previous Message Robert Haas 2012-08-09 14:11:08 Re: Inserting heap tuples in bulk in COPY