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

From: Alexander Lakhin <exclusion(at)gmail(dot)com>
To: Daniel Gustafsson <daniel(at)yesql(dot)se>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #18309: TOASTed entry in pg_subscription provokes an assertion failure
Date: 2024-01-24 16:00:00
Message-ID: 6a921555-8643-4fd8-443e-4471eb5868b4@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
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

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message gparc 2024-01-24 16:01:04 Re: BUG #18295: In PostgreSQL a unique index on targeted columns is sufficient to support a foreign key
Previous Message Laurenz Albe 2024-01-24 15:32:20 Re: BUG #18308: SQL query information_schema metadata got error: server process was terminated by signal 11: Segment