Re: BUG #15815: Upgraded from 9.6.8 > 9.6.12 on AWS Aurora: SELECTs causing segmentation fault

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: postgres-ca(at)byerquest(dot)com
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15815: Upgraded from 9.6.8 > 9.6.12 on AWS Aurora: SELECTs causing segmentation fault
Date: 2019-05-21 14:42:52
Message-ID: 3596.1558449772@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

PG Bug reporting form <noreply(at)postgresql(dot)org> writes:
> AWS Aurora, stable on 9.6.6/8 for a year, updated to 9.6.12:

> LOG: server process (PID 31294) was terminated by signal 11: Segmentation
> fault
> DETAIL: Failed process was running:
> simplied >>> SELECT value FROM {table} WHERE lower(substring(value,1,1000))
>> = '{string}'
> LOG: terminating any other active server processes

Huh. Can you get a stack trace from that?

https://wiki.postgresql.org/wiki/Generating_a_stack_trace_of_a_PostgreSQL_backend

Also, could we see the definition of the table (psql \d would be
helpful)?

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Euler Taveira 2019-05-21 14:46:18 Re: BUG #15815: Upgraded from 9.6.8 > 9.6.12 on AWS Aurora: SELECTs causing segmentation fault
Previous Message PG Bug reporting form 2019-05-21 14:26:24 BUG #15815: Upgraded from 9.6.8 > 9.6.12 on AWS Aurora: SELECTs causing segmentation fault