Re: More tests with USING INDEX replident and dropped indexes - Mailing list pgsql-hackers

From Michael Paquier
Subject Re: More tests with USING INDEX replident and dropped indexes
Date
Msg-id 20200826120851.GJ2017@paquier.xyz
Whole thread Raw
In response to Re: More tests with USING INDEX replident and dropped indexes  (Rahila <rahila.syed@2ndquadrant.com>)
Responses Re: More tests with USING INDEX replident and dropped indexes  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
On Tue, Aug 25, 2020 at 08:59:37PM +0530, Rahila wrote:
> Sorry, I didn't apply correctly.  The tests pass for me. In addition, I
> tested with partitioned tables.  It works as expected and makes the REPLICA
> IDENTITY 'n' for the partitions as well when an index on a partitioned
> table is dropped.

Indeed.  I have added a test for that.

While looking at this patch again, I noticed that the new tests for
contrib/test_decoding/ and the improvements for relreplident are
really two different bullet points, and that the new tests should not
be impacted as long as we switch to NOTHING the replica identity once
its index is dropped.  So, for now, I have applied the new decoding
tests with a first commit, and attached is an updated patch which
includes tests in the main regression test suite for
replica_identity.sql, which is more consistent with the rest as that's
the main place where we look at the state of pg_class.relreplident.
I'll go through this part again tomorrow, it is late here.
--
Michael

Attachment

pgsql-hackers by date:

Previous
From: ilmari@ilmari.org (Dagfinn Ilmari Mannsåker)
Date:
Subject: Re: LWLockAcquire and LockBuffer mode argument
Next
From: Tom Lane
Date:
Subject: Re: Strange behavior with polygon and NaN