Re: BUG #18309: TOASTed entry in pg_subscription provokes an assertion failure

Alexander Law <exclusion@gmail.com>

From: Alexander Lakhin <exclusion@gmail.com>
To: Daniel Gustafsson <daniel@yesql.se>, pgsql-bugs@lists.postgresql.org
Date: 2024-01-24T16:00:00Z
Lists: pgsql-bugs
Hello Daniel,

24.01.2024 18:24, Daniel Gustafsson wrote:
> This seems like a variation of the issue reported in the login event trigger
> thread at postgr.es/m/e2a0248e-5f32-af0c-9832-a90d303c2c61@gmail.com

Yes, it has the same root cause, but maybe it should be fixed differently.
I had also reported:
https://www.postgresql.org/message-id/18127-fe54b6a667f29658%40postgresql.org
but I'm not sure that all of these issues should be fixed by a single commit.
(Given that there are 7c38ef2a5 and 54b208f90 already.)
Though maybe I'm wrong here.

Best regards,
Alexander



Commits

  1. Ensure we have a snapshot when updating various system catalogs.