From: | Euler Taveira <euler(at)timbira(dot)com(dot)br> |
---|---|
To: | postgres-ca(at)byerquest(dot)com, 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:46:18 |
Message-ID: | CAHE3wgjAdMxsAteH_cEqxF_hRK0CtHWiQOb+Fhkcj4RMfaLjFA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Em ter, 21 de mai de 2019 às 11:27, PG Bug reporting form
<noreply(at)postgresql(dot)org> escreveu:
>
> AWS Aurora, stable on 9.6.6/8 for a year, updated to 9.6.12:
>
Aurora is a Postgres fork so you should report it to Amazon. However, ...
> 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
> FATAL: Can't handle storage runtime process crash
>
Could you reproduce it with stock Postgres? Could you provide a test case?
--
Euler Taveira Timbira -
http://www.timbira.com.br/
PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento
From | Date | Subject | |
---|---|---|---|
Next Message | Steve | 2019-05-21 15:35:04 | Re: BUG #15815: Upgraded from 9.6.8 > 9.6.12 on AWS Aurora: SELECTs causing segmentation fault |
Previous Message | Tom Lane | 2019-05-21 14:42:52 | Re: BUG #15815: Upgraded from 9.6.8 > 9.6.12 on AWS Aurora: SELECTs causing segmentation fault |