Re: Fwd: Re: proposal: schema variables

From: Marcos Pegoraro <marcos(at)f10(dot)com(dot)br>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Fwd: Re: proposal: schema variables
Date: 2025-01-17 21:30:40
Message-ID: CAB-JLwZG6rPK6dft0Pv1EXp2_C2JSWm4jz4WDeMf-_s6n5F32A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-performance

>
> > pá 17. 1. 2025 v 16:35 odesílatel Bruce Momjian <bruce(at)momjian(dot)us>
> napsal:
>
> Okay, good summary. Now, can people give feedback that they would want
> this committed to PostgreSQL?
>

I would love to have this functionality as soon as possible.
I already mentioned to Pavel that he did something very big, and
consequently difficult for anyone to commit, because these patches change a
lot of things in a lot of places.
Of course we want as much as possible, but who knows if a first, leaner
version was committed, with just session variables, so nothing related to
schemas, catalogs, grants, dumps, etc, just a variable in memory, only
that. It would be really cool, and certainly easier for a committer to
agree with the code. And if the first commit occurs, others can follow.

Remember that some people don't use PSQL, so they don't have \set
Even \set variables are not typed, so CREATE VARIABLE T AS
DOMAIN_NUMBER_BETWEEN_1_AND_5 is really cool.

regards
Marcos

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Marcos Pegoraro 2025-01-17 21:54:17 Re: Fwd: Re: proposal: schema variables
Previous Message Andres Freund 2025-01-17 21:29:14 Re: Purpose of wal_init_zero

Browse pgsql-performance by date

  From Date Subject
Next Message Marcos Pegoraro 2025-01-17 21:54:17 Re: Fwd: Re: proposal: schema variables
Previous Message Wolfgang Walther 2025-01-17 20:20:03 Re: Fwd: Re: proposal: schema variables