On Tue, Dec 14, 2021 at 07:10:49PM +0530, Ashutosh Bapat wrote:
> This code in RelationGetIndexList() is not according to that comment.
>
> if (replident == REPLICA_IDENTITY_DEFAULT && OidIsValid(pkeyIndex))
> relation->rd_replidindex = pkeyIndex;
> else if (replident == REPLICA_IDENTITY_INDEX && OidIsValid(candidateIndex))
> relation->rd_replidindex = candidateIndex;
> else
> relation->rd_replidindex = InvalidOid;
Yeah, the comment is wrong. If the index of a REPLICA_IDENTITY_INDEX
is dropped, I recall that the behavior is the same as
REPLICA_IDENTITY_NOTHING.
> Comment in code is one thing, but I think PG documentation is not
> covering the use case you tried. What happens when a replica identity
> index is dropped has not been covered either in ALTER TABLE
> https://www.postgresql.org/docs/13/sql-altertable.html or DROP INDEX
> https://www.postgresql.org/docs/14/sql-dropindex.html documentation.
Not sure about the DROP INDEX page, but I'd be fine with mentioning
that in the ALTER TABLE page in the paragraph related to REPLICA
IDENTITY. While on it, I would be tempted to switch this stuff to use
a list of <variablelist> for all the option values. That would be
much easier to read.
[ ... thinks a bit ... ]
FWIW, this brings back some memories, as of this thread:
https://www.postgresql.org/message-id/20200522035028.GO2355@paquier.xyz
See also commit fe7fd4e from August 2020, where some tests have been
added. I recall seeing this incorrect comment from last year's
thread and it may have been mentioned in one of the surrounding
threads.. Maybe I just let it go back then. I don't know.
--
Michael