Horton

Re: Re: proposal: schema variables

Pavel Stehule <pavel.stehule@gmail.com>

View thread
From: Pavel Stehule <pavel.stehule@gmail.com>
To: Bruce Momjian <bruce@momjian.us>
Cc: Marcos Pegoraro <marcos@f10.com.br>, jian he <jian.universality@gmail.com>, Dmitry Dolgov <9erthalion6@gmail.com>, Laurenz Albe <laurenz.albe@cybertec.at>, Erik Rijkers <er@xs4all.nl>, Michael Paquier <michael@paquier.xyz>, Amit Kapila <amit.kapila16@gmail.com>, DUVAL REMI <REMI.DUVAL@cheops.fr>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2025-05-20T20:28:31Z
Lists: pgsql-hackers, pgsql-performance

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Move WAL sequence code into its own file

  2. Add ExplainState argument to pg_plan_query() and planner().

  3. Don't include access/htup_details.h in executor/tuptable.h

  4. Refactor to avoid code duplication in transformPLAssignStmt.

  5. Avoid including commands/dbcommands.h in so many places

  6. Restrict psql meta-commands in plain-text dumps.

  7. Split func.sgml into more manageable pieces

  8. Fix squashing algorithm for query texts

  9. EXPLAIN: Always use two fractional digits for row counts.

  10. Preliminary refactoring of plpgsql expression construction.

  11. plpgsql: pure parser and reentrant scanner

  12. Add some sanity checks in executor for query ID reporting

  13. Fix misleading error message context

  14. Add macros for looping through a List without a ListCell.

Hi

út 20. 5. 2025 v 18:39 odesílatel Bruce Momjian <bruce@momjian.us> napsal:

> On Tue, May 20, 2025 at 01:33:18PM -0300, Marcos Pegoraro wrote:
> > Em ter., 20 de mai. de 2025 às 11:56, Bruce Momjian <bruce@momjian.us>
> > escreveu:
> >
> >     I will again ask why this patch set is being reposted when there is
> no
> >     plan to apply it to git master
> >
> > Too bad. I would love to have this functionality, from the user's point
> of view
> > there are problems where it would solve them wonderfully. I don't know
> > technically of what prevents it from being natively on core, but it
> would be
> > great, it would definitely be.
>
> My only point is that we should only be using email lists for work that
> is being actively worked on to be added to community Postgres.  There
> has been talk of a trimmed-down version of this being applied, but I
> don't see any work in that direction.
>

I sent a reduced version a few months ago - from 21 patches to 8 (and it
can be reduced to six if we postpone tools for detection ambiguity).
The timing was not perfect - the focus was and it is concentrated to finish
pg18.

I am very sorry if this topic and patches bother anyone. I am afraid if I
close it to some personal github, it will not be visible, and I am sure this
feature is missing in Postgres. Today we have few workarounds. Some
workarounds are not available everywhere, some workarounds cannot
be used for security. With integrated solutions some scenarios can be done
more easily, more secure, faster, more comfortable.  It is true, so
mentioned scenarios are not "hot" today. Stored procedures or RLS or
migration procedures from other databases are not extra common. But
who uses it, then he misses session variables.

This topic is difficult, because there is no common solution. SQL/PSM is
almost dead. T-SQL (and MySQL) design is weak and cannot be used for
security.
Oracle's design is joined with just one environment. And although almost
all widely used databases have supported session variables for decades, no
one design
is perfect. Proposed design is not perfect too (it introduces possible
ambiguity) , but I think it can support most wanted use cases (can be
enhanced in future),
and it is consistent with Postgres. There are more ways to reduce risk of
unwanted ambiguity to zero. But it increases the size of the patch.

Regards

Pavel







>
> This patch should be moved to a separate location where perhaps people
> can subscribe to updates when they are posted, perhaps github.
>
> --
>   Bruce Momjian  <bruce@momjian.us>        https://momjian.us
>   EDB                                      https://enterprisedb.com
>
>   Do not let urgent matters crowd out time for investment in the future.
>