From: | Dean Rasheed <dean(dot)a(dot)rasheed(at)gmail(dot)com> |
---|---|
To: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Doc updates for MERGE |
Date: | 2023-02-24 06:08:38 |
Message-ID: | CAEZATCWqHLcxab89ATMQZNGFG_mxDPM+jzkSbXKD3JYPfRGvtw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Attached is a patch fixing a few doc omissions for MERGE.
I don't think that it's necessary to update every place that could
possibly apply to MERGE, but there are a few places where we give a
list of commands that may be used in a particular context, and I think
those should mention MERGE, if it applies.
Also, there were a couple of other places where it seemed worth giving
slightly more detail about what happens for MERGE.
Regards,
Dean
Attachment | Content-Type | Size |
---|---|---|
merge-docs.patch | text/x-patch | 13.5 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Masahiko Sawada | 2023-02-24 06:16:10 | Re: Add index scan progress to pg_stat_progress_vacuum |
Previous Message | Masahiko Sawada | 2023-02-24 05:50:19 | Re: [PoC] Improve dead tuple storage for lazy vacuum |