| From: | Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> |
|---|---|
| To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Documenting MERGE INTO ONLY ... |
| Date: | 2022-12-08 15:26:52 |
| Message-ID: | CAEZATCU0XM-bJCvpJuVRU3UYNRqEBS6g4-zH=j9Ye0caX8F6uQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
While testing MERGE, I noticed that it supports inheritance
hierarchies and the ONLY keyword, but that isn't documented. Attached
is a patch to merge.sgml, borrowing text from update.sgml and
delete.sgml.
I note that there are also a couple of places early in the manual
(advanced.sgml and ddl.sgml) that also discuss inheritance, citing
SELECT, UPDATE and DELETE as examples of (already-discussed) commands
that support ONLY. However, since MERGE isn't mentioned until much
later in the manual, it's probably best to leave those as-is. They
don't claim to be complete lists of commands supporting ONLY, and it
would be a pain to make them that.
Regards,
Dean
| Attachment | Content-Type | Size |
|---|---|---|
| doc-merge-only.patch | text/x-patch | 2.8 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2022-12-08 16:31:59 | Re: Error-safe user functions |
| Previous Message | Tom Lane | 2022-12-08 14:38:55 | Re: Aggregate node doesn't include cost for sorting |