Re: Pgoutput not capturing the generated columns

From: Peter Eisentraut <peter(at)eisentraut(dot)org>
To: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, vignesh C <vignesh21(at)gmail(dot)com>
Cc: Peter Smith <smithpb2250(at)gmail(dot)com>, Shubham Khanna <khannashubham1197(at)gmail(dot)com>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Rajendra Kumar Dangwal <dangwalrajendra888(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org, euler(at)eulerto(dot)com
Subject: Re: Pgoutput not capturing the generated columns
Date: 2024-11-07 06:33:51
Message-ID: d718d219-dd47-4a33-bb97-56e8fc4da994@eisentraut.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 07.11.24 05:13, Amit Kapila wrote:
> On Wed, Nov 6, 2024 at 4:18 PM vignesh C <vignesh21(at)gmail(dot)com> wrote:
>>
>> The attached v50 version patch has the changes for the same.

Could you (everybody on this thread) please provide guidance how this
feature is supposed to interact with virtual generated columns [0]. I
don't think it's reasonably possible to replicate virtual generated
columns. I had previously suggested to make it more explicit that this
feature only works for stored generated columns (e.g., name the option
like that), but I don't see that this was considered.

[0]:
https://www.postgresql.org/message-id/flat/a368248e-69e4-40be-9c07-6c3b5880b0a6(at)eisentraut(dot)org

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2024-11-07 06:55:24 Re: Proposals for EXPLAIN: rename ANALYZE to EXECUTE and extend VERBOSE
Previous Message Tender Wang 2024-11-07 06:27:40 Re: Remove an obsolete comment in gistinsert()