| From: | Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | assam258(at)gmail(dot)com, Ayush Tiwari <ayushtiwari(dot)slg01(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [DEPARSE] EXPLAIN prints another ModifyTable's RETURNING aliases in a SubPlan |
| Date: | 2026-10-23 09:00:29 |
| Message-ID: | CAEZATCWwQn7Q4iX97z3fZZwHyxtddueB63TUMpBKfT9-n8SO6w@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, 23 Oct 2026 at 09:46, Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> wrote:
>
> RETURNING WITH (OLD AS o, NEW AS n)
> key,
> o.val1, -- Forces old.val1 to be returned regardless of old/new in
> -- triggering query
> n.val2, -- Forces new.val2 to be returned regardless of old/new in
> -- triggering query
Oops, I mis-remembered that. For the record, those comments should read
o.val1, -- Returns old.val1 if triggering query doesn't specify old/new
n.val2, -- Returns new.val2 if triggering query doesn't specify old/new
but that doesn't change any of the arguments that follow.
Regards,
Dean
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Álvaro Herrera | 2026-10-23 09:55:31 | Re: Resetting snapshots during the first phase of [CREATE |RE]INDEX CONCURRENTLY |
| Previous Message | Dean Rasheed | 2026-10-23 08:46:48 | Re: [DEPARSE] EXPLAIN prints another ModifyTable's RETURNING aliases in a SubPlan |