Re: UPDATE operation terminates logical replication receiver process due to an assertion
Justin Pryzby <pryzby@telsasoft.com>
From: Justin Pryzby <pryzby@telsasoft.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: v.davydov@postgrespro.ru, pgsql-hackers@lists.postgresql.org
Date: 2023-01-15T18:35:28Z
Lists: pgsql-hackers
On Sun, Jan 15, 2023 at 01:25:11PM -0500, Tom Lane wrote:
> Justin Pryzby <pryzby@telsasoft.com> writes:
> > On Thu, Jan 12, 2023 at 01:23:57PM +0300, v.davydov@postgrespro.ru wrote:
> >> TRAP: FailedAssertion("relinfo->ri_GeneratedExprs != NULL", File: "execUtils.c", Line: 1292)
>
> > Yeah, confirmed under master branch and v15.
>
> v15? That assert is from 8bf6ec3ba, which wasn't back-patched.
I misspoke, and had actually reproduced under master and v14:
TRAP: FailedAssertion("relinfo->ri_GeneratedExprs != NULL", File: "execUtils.c", Line: 1336, PID: 25692)
The assert isn't from 8bf6 (Improve handling of inherited GENERATED
expressions.), but rather:
commit 3f7836ff651ad710fef52fa87b248ecdfc6468dc
Author: Tom Lane <tgl@sss.pgh.pa.us>
Date: Thu Jan 5 14:12:17 2023 -0500
Fix calculation of which GENERATED columns need to be updated.
And in v14:
commit 8cd190e13a22dab12e86f7f1b59de6b9b128c784
Author: Tom Lane <tgl@sss.pgh.pa.us>
Date: Thu Jan 5 14:12:17 2023 -0500
Fix calculation of which GENERATED columns need to be updated.
--
Justin
Commits
-
Make new GENERATED-expressions code more bulletproof.
- a8f7687a0b86 15.2 landed
- a8b88c26f706 14.7 landed
- 787db4be947c 13.10 landed
- 3f244d020fbf 16.0 landed
-
Fix calculation of which GENERATED columns need to be updated.
- 8cd190e13a22 14.7 cited
- 3f7836ff651a 16.0 cited