Re: Schema variables - new implementation for Postgres 15

From: Julien Rouhaud <rjuju123(at)gmail(dot)com>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: dean(dot)a(dot)rasheed(at)gmail(dot)com, er(at)xs4all(dot)nl, joel(at)compiler(dot)org, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Schema variables - new implementation for Postgres 15
Date: 2022-09-06 10:23:12
Message-ID: 20220906102312.4npuynhyvd2dy6qj@jrouhaud
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

On Tue, Sep 06, 2022 at 08:43:59AM +0200, Pavel Stehule wrote:
> Hi
> After talking with Julian I removed "debug" fields name and nsname from
> SVariable structure. When it is possible it is better to read these fields
> from catalog without risk of obsoletely or necessity to refresh these
> fields. In other cases we display only oid of variable instead name and
> nsname (It is used just for debug purposes).

Thanks! I'm just adding back the forgotten Cc list.

Attachment Content-Type Size
v20220906-1-0001-catalog-support-for-session-variables.patch text/plain 98.2 KB
v20220906-1-0002-session-variables.patch text/plain 94.1 KB
v20220906-1-0003-LET-command.patch text/plain 38.5 KB
v20220906-1-0004-support-of-LET-command-in-PLpgSQL.patch text/plain 11.5 KB
v20220906-1-0005-DISCARD-VARIABLES-command.patch text/plain 3.2 KB
v20220906-1-0006-enhancing-psql-for-session-variables.patch text/plain 15.1 KB
v20220906-1-0007-possibility-to-dump-session-variables-by-pg_dump.patch text/plain 19.5 KB
v20220906-1-0008-typedefs.patch text/plain 1.6 KB
v20220906-1-0009-regress-tests-for-session-variables.patch text/plain 51.8 KB
v20220906-1-0010-this-patch-changes-error-message-column-doesn-t-exis.patch text/plain 23.7 KB
v20220906-1-0011-documentation.patch text/plain 42.2 KB

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2022-09-06 10:25:25 Re: test_decoding assertion failure for the loss of top-sub transaction relationship
Previous Message Aleksander Alekseev 2022-09-06 10:18:52 Re: [PATCH] Clarify the comments about varlena header encoding