Re: Virtual generated columns

From: Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com>
To: Peter Eisentraut <peter(at)eisentraut(dot)org>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, jian he <jian(dot)universality(at)gmail(dot)com>
Subject: Re: Virtual generated columns
Date: 2025-01-27 12:42:18
Message-ID: CAEZATCX6SHevKrVfAOq+88b4Ysm4Rqq2yeO6He3N0pttEbjYag@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, 27 Jan 2025 at 09:59, Peter Eisentraut <peter(at)eisentraut(dot)org> wrote:
>
> Here is an updated patch that integrates the above changes and also
> makes some adjustments now that the logical replication configuration
> questions are resolved. I think this is complete now.
>

In struct ResultRelInfo, the following field is added:

int ri_NumGeneratedNeededI;
int ri_NumGeneratedNeededU;

+ /* true if the above have been computed */
+ bool ri_Generated_valid;
+

but that doesn't really seem to be accurate, because it's set to true
by ExecInitGenerated() whether it's called with CMD_INSERT or
CMD_UPDATE, so it will be true before both the other fields are
computed. It's used from ExecGetExtraUpdatedCols() as an indicator
that ri_extraUpdatedCols is valid, but it looks like that might not be
the case, if ExecInitGenerated() was only called with CMD_INSERT.

I'm not sure if that represents an actual bug, but it looks wrong. It
should perhaps be called "ri_extraUpdatedCols_valid", and only set to
true when ExecInitGenerated() is called with CMD_UPDATE, and
ri_extraUpdatedCols is populated.

Regards,
Dean

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Nitin Jadhav 2025-01-27 12:45:09 Back patch of Remove durable_rename_excl()
Previous Message Tatsuo Ishii 2025-01-27 11:51:15 Re: Add RESPECT/IGNORE NULLS and FROM FIRST/LAST options