Re: BUG #18309: TOASTed entry in pg_subscription provokes an assertion failure - Mailing list pgsql-bugs

From Daniel Gustafsson
Subject Re: BUG #18309: TOASTed entry in pg_subscription provokes an assertion failure
Date
Msg-id CA41AE30-E473-4B66-B389-489E6E46C39F@yesql.se
Whole thread Raw
In response to BUG #18309: TOASTed entry in pg_subscription provokes an assertion failure  (PG Bug reporting form <noreply@postgresql.org>)
Responses Re: BUG #18309: TOASTed entry in pg_subscription provokes an assertion failure  (Alexander Lakhin <exclusion@gmail.com>)
List pgsql-bugs
> On 24 Jan 2024, at 13:00, PG Bug reporting form <noreply@postgresql.org> wrote:
>
> The following bug has been logged on the website:
>
> Bug reference:      18309
> Logged by:          Alexander Lakhin
> Email address:      exclusion@gmail.com
> PostgreSQL version: 16.1
> Operating system:   Ubuntu 22.04
> Description:
>
> When a pg_subscription entry contains a TOASTed field, e.g., subconninfo,
> several operations with the subscription trigger an assertion failure.
>
> For example, with the following modification of test 029_on_error.pl:
> -my $publisher_connstr = $node_publisher->connstr . ' dbname=postgres';
> +my $publisher_connstr = $node_publisher->connstr . ' dbname=postgres
> password=' . join('', map {chr(65 + rand 26)} (1 .. 10000));
>
> I get an assertion failure with the stack:

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

--
Daniel Gustafsson




pgsql-bugs by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: BUG #18295: In PostgreSQL a unique index on targeted columns is sufficient to support a foreign key
Next
From: Laurenz Albe
Date:
Subject: Re: BUG #18295: In PostgreSQL a unique index on targeted columns is sufficient to support a foreign key