Re: Accommodate startup process in a separate ProcState array slot instead of in MaxBackends slots.

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>
Cc: Yura Sokolov <y(dot)sokolov(at)postgrespro(dot)ru>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Accommodate startup process in a separate ProcState array slot instead of in MaxBackends slots.
Date: 2022-03-28 19:16:55
Message-ID: CA+TgmoarpX4e7OgmYpWebanpfafTA01CXyKN7q7roKKYnkLeeg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Mar 26, 2022 at 2:23 AM Bharath Rupireddy
<bharath(dot)rupireddyforpostgres(at)gmail(dot)com> wrote:
> Thanks. It makes sense to put the comment in SInvalShmemSize.
> Attaching v2 patch. Please review it.

How about this version, which I have edited lightly for grammar?

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

Attachment Content-Type Size
sinvalshmemsize-comment-rmh.patch application/octet-stream 783 bytes

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2022-03-28 19:27:25 Re: SQL/JSON: functions
Previous Message Tom Lane 2022-03-28 19:14:04 Re: Granting SET and ALTER SYSTE privileges for GUCs