From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Michael Paquier <michael(at)paquier(dot)xyz> |
Cc: | melody_xiaodi(at)sina(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #17563: exception " Segmentation fault" occured when i executed 'reindex index concurrently' in pg12.0 |
Date: | 2022-08-01 14:09:16 |
Message-ID: | 1699770.1659362956@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Michael Paquier <michael(at)paquier(dot)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 exited
>> 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_PostgreSQL_backend
From | Date | Subject | |
---|---|---|---|
Next Message | PG Bug reporting form | 2022-08-01 14:54:30 | BUG #17564: Planner bug in combination of generate_series(), unnest() and ORDER BY |
Previous Message | Richard Guo | 2022-08-01 10:51:26 | Re: Re[2]: BUG #17561: Server crashes on executing row() with very long argument list |