Fix for segfault in logical replication on master - Mailing list pgsql-hackers

From Mark Dilger
Subject Fix for segfault in logical replication on master
Date
Msg-id 4C99A862-69C8-431F-960A-81B1151F1B89@enterprisedb.com
Whole thread Raw
Responses RE: Fix for segfault in logical replication on master  ("osumi.takamichi@fujitsu.com" <osumi.takamichi@fujitsu.com>)
List pgsql-hackers
Hi Amit,

In commit e7eea52b2d, you introduced a new function, RelationGetIdentityKeyBitmap(), which uses some odd logic for
determiningif a relation has a replica identity index.  That code segfaults under certain conditions.  A test case to
demonstratethat is attached.  Prior to patching the code, this new test gets stuck waiting for replication to finish,
whichnever happens.  You have to break out of the test and check tmp_check/log/021_no_replica_identity_publisher.log. 

I believe this bit of logic in src/backend/utils/cache/relcache.c:

      indexDesc = RelationIdGetRelation(relation->rd_replidindex);
      for (i = 0; i < indexDesc->rd_index->indnatts; i++)

is unsafe without further checks, also attached.

Would you mind taking a look?



—
Mark Dilger
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company




Attachment

pgsql-hackers by date:

Previous
From: Amit Langote
Date:
Subject: Re: Skip partition tuple routing with constant partition key
Next
From: Zhihong Yu
Date:
Subject: Re: Skip partition tuple routing with constant partition key