Re: REL_12_STABLE crashing with assertion failure in ExtractReplicaIdentity

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Hadi Moshayedi <hadi(at)moshayedi(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: REL_12_STABLE crashing with assertion failure in ExtractReplicaIdentity
Date: 2019-08-17 05:43:45
Message-ID: 25222.1566020625@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andres Freund <andres(at)anarazel(dot)de> writes:
> On 2019-08-16 09:44:15 -0700, Hadi Moshayedi wrote:
>> It seems that sometimes when DELETE cascades to referencing tables we fail
>> to acquire locks on replica identity index.

> I suspect this "always" has been broken, it's just that we previously
> didn't have checks in place that detect these cases. I don't think it's
> likely to cause actual harm, due to the locking on the table itself when
> dropping indexes etc. But we still should fix it.

Yeah ... see the discussion leading up to 9c703c169,

https://www.postgresql.org/message-id/flat/19465.1541636036%40sss.pgh.pa.us

We didn't pull the trigger on removing the CMD_DELETE exception here,
but I think the handwriting has been on the wall for some time.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Antonin Houska 2019-08-17 06:16:06 Re: [Proposal] Table-level Transparent Data Encryption (TDE) and Key Management Service (KMS)
Previous Message tara 2019-08-17 04:17:07 [PATCH] minor doc fix for create-role