| From: | Jeff Davis <pgsql(at)j-davis(dot)com> |
|---|---|
| To: | Gurjeet Singh <gurjeet(at)singh(dot)im>, Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> |
| Cc: | Isaac Morland <isaac(dot)morland(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: MERGE ... RETURNING |
| Date: | 2023-07-21 18:30:22 |
| Message-ID: | fff7a24e740d8116e4573dcf9321b35730022263.camel@j-davis.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, 2023-07-20 at 23:19 -0700, Gurjeet Singh wrote:
> Plus, if we were able to make it work as SQL syntax, it's very likely
> we can use the same technique to implement BEFORE and AFTER behaviour
> in UPDATE ... RETURNING that the old thread could not accomplish a
> decade ago.
To clarify, I don't think having a special table alias will require any
changes in gram.y and I don't consider it a syntactical change.
I haven't looked into the implementation yet.
Regards,
Jeff Davis
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2023-07-21 19:17:50 | Re: Use of additional index columns in rows filtering |
| Previous Message | Tom Lane | 2023-07-21 17:41:56 | Re: Issue in _bt_getrootheight |