From: Alexander Lakhin <exclusion@gmail.com>
To: Daniel Gustafsson <daniel@yesql.se>
To: pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18309: TOASTed entry in pg_subscription provokes an assertion failure
Date: Wed, 24 Jan 2024 19:00:00 +0300
Message-ID: <6a921555-8643-4fd8-443e-4471eb5868b4@gmail.com> (raw)
In-Reply-To: <CA41AE30-E473-4B66-B389-489E6E46C39F@yesql.se>
References: <18309-c0bf914950c46692@postgresql.org>
<CA41AE30-E473-4B66-B389-489E6E46C39F@yesql.se>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-bugs@postgresql.org
Cc: exclusion@gmail.com, daniel@yesql.se, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18309: TOASTed entry in pg_subscription provokes an assertion failure
In-Reply-To: <6a921555-8643-4fd8-443e-4471eb5868b4@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox