From: Tom Lane <tgl@sss.pgh.pa.us>
To: Michael Paquier <michael@paquier.xyz>
cc: melody_xiaodi@sina.com, pgsql-bugs@lists.postgresql.org
Subject: Re: BUG #17563: exception " Segmentation fault" occured when i
 executed 'reindex index concurrently' in pg12.0
In-reply-to: <YueHdMn3YMv88OVE@paquier.xyz>
References: <17563-2aeaf763e2edfa83@postgresql.org>
 <YueHdMn3YMv88OVE@paquier.xyz>
Comments: In-reply-to Michael Paquier <michael@paquier.xyz>
	message dated "Mon, 01 Aug 2022 16:57:40 +0900"
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <1699769.1659362956.1@sss.pgh.pa.us>
Content-Transfer-Encoding: quoted-printable
Date: Mon, 01 Aug 2022 10:09:16 -0400
Message-ID: <1699770.1659362956@sss.pgh.pa.us>
Archived-At: 
 <https://www.postgresql.org/message-id/1699770.1659362956%40sss.pgh.pa.us>
Precedence: bulk

Michael Paquier <michael@paquier.xyz> writes:
> On Mon, Aug 01, 2022 at 02:39:36AM +0000, PG Bug reporting form wrote:
>> i executed the sql below to rebuild an index in my pg database(version =
12.0)
>> :
>> psql> reindex index concurrently myindex;
>> an unexpectend error was reported and all of the client processes exite=
d
>> abnormally .

> 12.0 is 3 years behind in terms of bug fixes, 12.11 being the latest
> minor version available.  So you may want to check with this version
> first and see if the problem reproduces there are well.

Yeah, and REINDEX CONCURRENTLY has been one of the more-often-fixed
features :-(.  If it does still reproduce with 12.11, please see if
you can get a stack trace from the crash [1].  Also, does it crash
if you omit CONCURRENTLY?

			regards, tom lane

[1] https://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_Postgre=
SQL_backend