| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
| Cc: | Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: SIGSEGV in BRIN autosummarize |
| Date: | 2017-10-17 07:51:33 |
| Message-ID: | 20171017075133.6z42o4z5qhm65ikb@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Justin Pryzby wrote:
> On Sun, Oct 15, 2017 at 02:44:58PM +0200, Tomas Vondra wrote:
> > Thanks, but I'm not sure that'll help, at this point. We already know
> > what happened (corrupted memory), we don't know "how". And core files
> > are mostly just "snapshots" so are not very useful in answering that :-(
>
> Is there anything I should be saving for these or hints how else to debug?
Sorry, I had missed this report. I'll look into it today.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2017-10-17 10:02:00 | Re: [COMMITTERS] pgsql: Fix traversal of half-frozen update chains |
| Previous Message | Masahiko Sawada | 2017-10-17 07:03:19 | Re: [PATCH] pageinspect function to decode infomasks |