Justin Pryzby writes:
> On Sun, Jan 15, 2023 at 01:25:11PM -0500, Tom Lane wrote:
>> v15? That assert is from 8bf6ec3ba, which wasn't back-patched.
> The assert isn't from 8bf6 (Improve handling of inherited GENERATED
> expressions.), but rather:
> commit 3f7836ff651ad710fef52fa87b248ecdfc6468d
On Sun, Jan 15, 2023 at 01:25:11PM -0500, Tom Lane wrote:
> Justin Pryzby writes:
> > On Thu, Jan 12, 2023 at 01:23:57PM +0300, v.davy...@postgrespro.ru wrote:
> >> TRAP: FailedAssertion("relinfo->ri_GeneratedExprs != NULL", File:
> >> "execUtils.c", Line: 1292)
>
> > Yeah, confirmed under maste
Justin Pryzby writes:
> On Thu, Jan 12, 2023 at 01:23:57PM +0300, v.davy...@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 b
Justin Pryzby writes:
> Yeah, confirmed under master branch and v15.
> Tom ?
Yeah, sorry, I've been absorbed in $other_stuff. Will look
at this soon. My guess is that this logrep code path is
missing the necessary setup operation.
regards, tom lane
On Thu, Jan 12, 2023 at 01:23:57PM +0300, v.davy...@postgrespro.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=postg