From: Tom Lane <tgl@sss.pgh.pa.us>
To: Sergey Belyashov <sergey.belyashov@gmail.com>
cc: Tomas Vondra <tomas@vondra.me>, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #18815: Logical replication worker Segmentation fault
In-reply-to: <911898.1739823180@sss.pgh.pa.us>
References: <18815-2a0407cc7f40b327@postgresql.org>
 <832225.1739810351@sss.pgh.pa.us>
 <CAOe0RDwbowSGv8qeuqyHzJndtwV5JyPEG4YwmaAvgquC=gjz+Q@mail.gmail.com>
 <906545.1739821437@sss.pgh.pa.us> <911898.1739823180@sss.pgh.pa.us>
Comments: In-reply-to Tom Lane <tgl@sss.pgh.pa.us>
	message dated "Mon, 17 Feb 2025 15:13:00 -0500"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <917261.1739825850.1@sss.pgh.pa.us>
Date: Mon, 17 Feb 2025 15:57:30 -0500
Message-ID: <917262.1739825850@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/917262.1739825850%40sss.pgh.pa.us>
Precedence: bulk

Further to this ... I'd still really like to have a reproducer.
While brininsertcleanup is clearly being less robust than it should
be, I now suspect that there is another bug somewhere further down
the call stack.  We're getting to this point via ExecCloseIndices,
and that should be paired with ExecOpenIndices, and that would have
created a fresh IndexInfo.  So it looks a lot like some path in a
logrep worker is able to call ExecCloseIndices twice on the same
working data.  That would probably lead to a "releasing a lock you
don't own" error if we weren't hitting this crash first.

			regards, tom lane