From: | Michael Paquier <michael(at)paquier(dot)xyz> |
---|---|
To: | "wangw(dot)fnst(at)fujitsu(dot)com" <wangw(dot)fnst(at)fujitsu(dot)com> |
Cc: | Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Confused comment about drop replica identity index |
Date: | 2021-12-20 11:11:04 |
Message-ID: | YcBkyHOBwSljDkCZ@paquier.xyz |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Dec 20, 2021 at 03:46:13AM +0000, wangw(dot)fnst(at)fujitsu(dot)com wrote:
> Here is a patch to correct wrong comment about
> REPLICA_IDENTITY_INDEX, And improve the pg-doc.
That's mostly fine. I have made some adjustments as per the
attached.
+ The default for non-system tables. Records the old values of the columns
+ of the primary key, if any. The default for non-system tables.
The same sentence is repeated twice.
+ Records no information about the old row.(This is the
default for system tables.)
For consistency with the rest, this could drop the parenthesis for the
second sentence.
+ <term><literal>USING INDEX index_name</literal></term>
This should use <replaceable> as markup for index_name.
Pondering more about this thread, I don't think we should change the
existing behavior in the back-branches, but I don't have any arguments
about doing such changes on HEAD to help the features being worked
on, either. So I'd like to apply and back-patch the attached, as a
first step, to fix the inconsistency.
--
Michael
Attachment | Content-Type | Size |
---|---|---|
v2-0001-Correct-comment-and-documentation-about-REPLICA_I.patch | text/x-diff | 3.6 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2021-12-20 11:21:51 | Re: pg_upgrade should truncate/remove its logs before running |
Previous Message | Yugo NAGATA | 2021-12-20 10:45:42 | Re: Allow DELETE to use ORDER BY and LIMIT/OFFSET |