Re: Segmentation fault in PostgreSQL 17.7 during REINDEX TABLE CONCURRENTLY

Hi Ana

On 18/03/2026 10:54, Ana Almeida wrote:
> 2026-03-17 18:19:55.244 WAT [2261667] LOG:  server process (PID 2382873)
> was terminated by signal 11: Segmentation fault
>
> 2026-03-17 18:19:55.244 WAT [2261667] DETAIL:  Failed process was
> running: REINDEX TABLE CONCURRENTLY sibs.purchases;
>
> 2026-03-17 18:19:55.244 WAT [2261667] LOG:  terminating any other active
> server processes
>
> 2026-03-17 18:19:55.257 WAT [2261667] LOG:  all server processes
> terminated; reinitializing
>
> 2026-03-17 18:19:55.354 WAT [2382972] LOG:  database system was
> interrupted; last known up at 2026-03-17 18:18:58 WAT
>
> 2026-03-17 18:19:55.449 WAT [2382972] LOG:  database system was not
> properly shut down; automatic recovery in progress
>
> 2026-03-17 18:19:55.457 WAT [2382972] LOG:  redo starts at 310/8142BEC0
>
> 2026-03-17 18:19:56.352 WAT [2382972] LOG:  invalid record length at
> 310/988BAA18: expected at least 24, got 0
>
> 2026-03-17 18:19:56.352 WAT [2382972] LOG:  redo done at 310/988BA9E0
> system usage: CPU: user: 0.28 s, system: 0.34 s, elapsed: 0.89 s
>
> 2026-03-17 18:19:56.360 WAT [2382973] LOG:  checkpoint starting: end-of-
> recovery immediate wait

I was unable to reproduce the bug. Could you share a bit more data on
the table and indexes that caused the system crash?

Best, Jim