From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Thom Brown <thom(at)linux(dot)com> |
Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Noah Misch <noah(at)leadboat(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: assessing parallel-safety |
Date: | 2015-03-20 15:02:56 |
Message-ID: | CA+TgmoZdAX56ii_EWK6q7GBUNgpam0=RCaLaL70umARbycu92Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Mar 20, 2015 at 10:24 AM, Thom Brown <thom(at)linux(dot)com> wrote:
> 2015-03-20 14:19:31 GMT [4273]: [78-1] user=,db=,client= DEBUG:
> server process (PID 4285) was terminated by signal 11: Segmentation
> fault
Any chance you can get us a stack backtrace of this crash?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Thom Brown | 2015-03-20 15:08:15 | Re: assessing parallel-safety |
Previous Message | Vladimir Borodin | 2015-03-20 15:00:16 | Re: [pgadmin-support] Issue with a hanging apply process on the replica db after vacuum works on primary |