Re: On login trigger: take three
| От | Robert Haas |
|---|---|
| Тема | Re: On login trigger: take three |
| Дата | |
| Msg-id | CA+TgmoZWtP2Pr8PurLV2zH+a_WM6cUcXAwBcWpS9Vw5QUfbnPQ@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: On login trigger: take three (Alexander Korotkov <aekorotkov@gmail.com>) |
| Ответы |
Re: On login trigger: take three
|
| Список | pgsql-hackers |
On Thu, Oct 12, 2023 at 6:54 PM Alexander Korotkov <aekorotkov@gmail.com> wrote: > On Thu, Oct 12, 2023 at 8:35 PM Robert Haas <robertmhaas@gmail.com> wrote: > > Doesn't that mean that if you create the first login trigger in a > > database and leave the transaction open, nobody can connect to that > > database until the transaction ends? > > It doesn't mean that, because when trying to reset the flag v44 does > conditional lock. So, if another transaction is holding the log we > will just skip resetting the flag. So, the flag will be cleared on > the first connection after that transaction ends. But in the scenario I am describing the flag is being set, not reset. -- Robert Haas EDB: http://www.enterprisedb.com
В списке pgsql-hackers по дате отправления: