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

From Jelte Fennema-Nio
Subject Re: Add new protocol message to change GUCs for usage with future protocol-only GUCs
Date
Msg-id CAGECzQTk8qAt3dfU7NuEv7nvAH+ckk4M28LFYpxs7W1Za=+eMg@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 Tue, 18 Feb 2025 at 09:51, Jelte Fennema-Nio <postgres@jeltef.nl> wrote:
> Rebased it, and moved some of the new header definitions around to
> hopefully not have to rebase again.

This required another rebase, but I've decided that I think it'll be
most fruitful to continue the discussion on protocol changes in the
thread about longer cancel keys[1]. Over there I've removed patch 5, 7
and 8 and rebased Heikki's changes on top of the rest. I hope this'll
let us make some progress sooner.

[1]:
https://www.postgresql.org/message-id/flat/CAGECzQTfc_O%2BHXqAo5_-xG4r3EFVsTefUeQzSvhEyyLDba-O9w%40mail.gmail.com#b88eb8989587b1f3acef5c00736b097f



pgsql-hackers by date:

Previous
From: Alexander Lakhin
Date:
Subject: Re: generic plans and "initial" pruning
Next
From: Richard Guo
Date:
Subject: Re: Virtual generated columns