Re: UPDATE operation terminates logical replication receiver process due to an assertion

On Thu, Jan 12, 2023 at 01:23:57PM +0300, v(dot)davydov(at)postgrespro(dot)ru wrote:
> Dear all,
>
> I think I've found a problem in logical replication that was introduced
> recently in the patch:
>
> Fix calculation of which GENERATED columns need to be updated
> https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=3f7836ff651ad710fef52fa87b248ecdfc6468dc

> There is an assertion which accidentally terminates logical replication
> worker process. The assertion was introduced in the patch. To reproduce the
> problem Postgres should be compiled with enabled assertions. The problem
> appears when executing UPDATE operation on a non-empty table with GENERATED
> columns and a BEFORE UPDATE trigger. The problem seems to appear on the
> latest snapshots of 13 and 14 versions (sorry, I haven't tested other
> versions).
>
> Stack:
> ------
> TRAP: FailedAssertion("relinfo->ri_GeneratedExprs != NULL", File: "execUtils.c", Line: 1292)

Yeah, confirmed under master branch and v15.

Tom ?

--
Justin