Re: Add new protocol message to change GUCs for usage with future protocol-only GUCs - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Add new protocol message to change GUCs for usage with future protocol-only GUCs
Date
Msg-id CA+TgmoYOZ4kQsAn8S40-g7fsWwqfB3jZPsZerFgH4u4MYu9-rA@mail.gmail.com
Whole thread Raw
In response to Add new protocol message to change GUCs for usage with future protocol-only GUCs  (Jelte Fennema-Nio <me@jeltef.nl>)
List pgsql-hackers
On Wed, Aug 14, 2024 at 2:04 PM Jelte Fennema-Nio <postgres@jeltef.nl> wrote:
> Applied all 0002 feedback. Although I used Min(proto,
> PG_PROTOCOL_LATEST) because Max results in the wrong value.

Picky, picky. :-)

Committed.

> Makes sense. I'm not in too much of a hurry with this specific one. So
> I'll leave it like this for now and hopefully someone else responds.
> If this becomes close to being the final unmerged patch of this
> patchset, I'll probably cut my losses and create a patch that adds a
> function instead.

Maybe reorder the series to put that one later then.

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



pgsql-hackers by date:

Previous
From: Nathan Bossart
Date:
Subject: Re: Adding clarification to description of IPC wait events XactGroupUpdate and ProcArrayGroupUpdate
Next
From: Alexander Lakhin
Date:
Subject: Re: Remove dependence on integer wrapping