Re: Table AM modifications to accept column projection lists - Mailing list pgsql-hackers

From Jacob Champion
Subject Re: Table AM modifications to accept column projection lists
Date
Msg-id e82d48a8bbd617508f1e51606db9de7a63466636.camel@vmware.com
Whole thread Raw
In response to Re: Table AM modifications to accept column projection lists  (Aleksander Alekseev <aleksander@timescale.com>)
Responses Re: Table AM modifications to accept column projection lists
List pgsql-hackers
On Tue, 2021-06-01 at 15:38 +0300, Aleksander Alekseev wrote:
> I came across this patch and noticed that it rotted a little,
> especially after removing inheritance_planner() in 86dc9005. I
> managed to resolve the conflicts on current `master` (eb89cb43), see
> the attached patch. The code compiles but doesn't pass the tests. I'm
> currently in the process of reviewing it and didn't figure out what
> the issue is yet. Just wanted to let you know.

Hi Alexsander, thanks!

In your patch's transformInsertStmt(), I see what I think is an
extraneous call to transformReturningList() right before the ON
CONFLICT processing. That call is already done later in the function,
during the RETURNING processing (this change came in with 6c0373ab77).
Other than that, your rebased patch looks the same as mine.

>  I also believe changing the patch status to "Waiting on Author"
> would be appropriate.

Agreed. I'm going to double-check with Deep that the new calls
to table_tuple_fetch_row_version() should be projecting the full row,
then post an updated patch some time next week.

Thanks again!
--Jacob

pgsql-hackers by date:

Previous
From: Jeremy Schneider
Date:
Subject: Re: logical decoding bug: segfault in ReorderBufferToastReplace()
Next
From: Alvaro Herrera
Date:
Subject: Re: Move pg_attribute.attcompression to earlier in struct for reduced size?