Re: Schema variables - new implementation for Postgres 15

Pavel Stehule <pavel.stehule@gmail.com>

From: Pavel Stehule <pavel.stehule@gmail.com>

To: Julien Rouhaud <rjuju123@gmail.com>

Cc: Dean Rasheed <dean.a.rasheed@gmail.com>, Joel Jacobson <joel@compiler.org>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>

Date: 2022-01-24T11:33:11Z

Lists: pgsql-hackers

Commits

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

Allow underscores in integer and numeric constants.
- faff8f8e47f1 16.0 cited
Remove special outfuncs/readfuncs handling of RangeVar.catalogname.
- 3cece34be842 16.0 cited
Remove extra space from dumped ALTER DEFAULT PRIVILEGES.
- 2af33369e794 16.0 cited
Create FKs properly when attaching table as partition
- b0284bfb1db5 16.0 cited
psql: improve tab-complete's handling of variant SQL names.
- 02b8048ba5dc 15.0 cited

Attachments

0002-column-doesn-t-exists-message.patch (text/x-patch) patch 0002
0001-session-variables.patch (text/x-patch) patch 0001

Hi

ne 23. 1. 2022 v 16:06 odesílatel Julien Rouhaud <rjuju123@gmail.com>
napsal:

> Hi,
>
> Le dim. 23 janv. 2022 à 22:34, Pavel Stehule <pavel.stehule@gmail.com> a
> écrit :
>
>> I tested it now. a sinval message is waiting on the transaction end.  So
>> when a variable is used, then it is working fine until the transaction ends.
>> But when the session makes some DDL, then send sinval to self, and at
>> this moment, the variable can be dropped before the transaction ends.
>>
>
> a backend can accept sinval in very common scenarios, like acquiring a
> heavyweight lock. That includes accessing a relation thats not in the
> catcache, so that's really critical to have a protection here.
>

here is updated patch with locking support

Regards

Pavel