Re: Refactoring postmaster's code to cleanup after child exit

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Refactoring postmaster's code to cleanup after child exit
Date: 2024-09-06 13:32:04
Message-ID: CA+TgmoY97LtyT1c+sP7oe11TG9BwaJpnSmnVmueoCigt+3KEeQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Sep 6, 2024 at 9:13 AM Heikki Linnakangas <hlinnaka(at)iki(dot)fi> wrote:
> It's currently possible to have up to 2 * max_connections backends in
> the authentication phase. We would have to change that behaviour, or
> make the PGPROC array 2x larger.

I know I already said this elsewhere, but in case it got lost in the
shuffle, +1 for changing this, unless somebody can make a compelling
argument why 2 * max_connections isn't WAY too many.

--
Robert Haas
EDB: http://www.enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message David Rowley 2024-09-06 13:37:20 Re: Optimize WindowAgg's use of tuplestores
Previous Message Heikki Linnakangas 2024-09-06 13:13:43 Re: Refactoring postmaster's code to cleanup after child exit