| From: | Julien Rouhaud <rjuju123(at)gmail(dot)com> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>, Joel Jacobson <joel(at)compiler(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Schema variables - new implementation for Postgres 15 |
| Date: | 2022-01-23 15:06:15 |
| Message-ID: | CAOBaU_YrgXc=8GtcrY3UxWqcW0mP1BRkK0d8S1rqw99JOAHbxQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
Le dim. 23 janv. 2022 à 22:34, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)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.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2022-01-23 15:16:42 | Re: current_schema will not use an text index ? |
| Previous Message | Pavel Stehule | 2022-01-23 14:33:33 | Re: Schema variables - new implementation for Postgres 15 |