On Tue, Oct 10, 2023 at 3:43 PM Alexander Korotkov <aekorot...@gmail.com> wrote: > Yep, in v43 it worked that way. One transaction has to wait for > another finishing update of pg_database tuple, then fails. This is > obviously ridiculous. Since overlapping setters of flag will have to > wait anyway, I changed lock mode in v44 for them to > AccessExclusiveLock. Now, waiting transaction then sees the updated > tuple and doesn't fail.
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? -- Robert Haas EDB: http://www.enterprisedb.com
