Re: SQL:2011 application time

From: jian he <jian(dot)universality(at)gmail(dot)com>
To: Paul Jungwirth <pj(at)illuminatedcomputing(dot)com>
Cc: Peter Eisentraut <peter(at)eisentraut(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: SQL:2011 application time
Date: 2023-12-06 13:22:07
Message-ID: CACJufxF2HMBZJ-LV5BTooRf-OPMj9RBwFoLxS0ThVTc14bX=4w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Dec 3, 2023 at 2:11 AM Paul Jungwirth
<pj(at)illuminatedcomputing(dot)com> wrote:
>
> v19 patch series attached, rebased to a11c9c42ea.
>

this TODO:
* TODO: It sounds like FOR PORTION OF might need to do something here too?
based on comments on ExprContext. I refactor a bit, and solved this TODO.

tring to the following TODO:
// TODO: Need to save context->mtstate->mt_transition_capture? (See
comment on ExecInsert)

but failed.
I also attached the trial, and also added the related test.

You can also use the test to check portion update with insert trigger
with "referencing old table as old_table new table as new_table"
situation.

Attachment Content-Type Size
v1-0001-set eval targetrange in per-output-tuple context.patch text/x-patch 1.4 KB
v1-0001-trying-to-save-mt_transition_capture-while-ExecIn.patch text/x-patch 10.8 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2023-12-06 13:25:16 Re: Partial aggregates pushdown
Previous Message Anthonin Bonnefoy 2023-12-06 13:20:37 Re: Possible segfault when sending notification within a ProcessUtility hook