Re: Add new protocol message to change GUCs for usage with future protocol-only GUCs

From: Jelte Fennema-Nio <me(at)jeltef(dot)nl>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Jacob Burroughs <jburroughs(at)instructure(dot)com>, Dave Cramer <davecramer(at)gmail(dot)com>, Peter Smith <smithpb2250(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, "Andrey M(dot) Borodin" <x4mmm(at)yandex-team(dot)ru>, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Jeff Davis <pgsql(at)j-davis(dot)com>, Peter Eisentraut <peter(at)eisentraut(dot)org>
Subject: Re: Add new protocol message to change GUCs for usage with future protocol-only GUCs
Date: 2024-05-25 10:43:46
Message-ID: CAGECzQSoWWYiaz9TNCcY7wQLa58mq-gcoHLJ9AGhd3HGKh52dQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

(pressed send to early)

On Sat, 25 May 2024 at 12:39, Jelte Fennema-Nio <me(at)jeltef(dot)nl> wrote:
> But again if I'm alone in this, then I don't

... mind budging on this to move this decision along. Using _pq_.xxx
parameters for all protocol changes would totally be acceptable to me.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Pavel Stehule 2024-05-25 10:50:45 Re: Schema variables - new implementation for Postgres 15
Previous Message Jelte Fennema-Nio 2024-05-25 10:39:58 Re: Add new protocol message to change GUCs for usage with future protocol-only GUCs