Re: [BUGS] BUG #14781: server process was terminated by signal 11: Segmentation fault - Mailing list pgsql-bugs

From Tom Lane
Subject Re: [BUGS] BUG #14781: server process was terminated by signal 11: Segmentation fault
Date
Msg-id 28874.1502902609@sss.pgh.pa.us
Whole thread Raw
In response to Re: [BUGS] BUG #14781: server process was terminated by signal 11:Segmentation fault  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: [BUGS] BUG #14781: server process was terminated by signal 11:Segmentation fault
List pgsql-bugs
Alvaro Herrera <alvherre@2ndquadrant.com> writes:
> Tom Lane wrote:
>> If you want to push this forward rather than wait for somebody else
>> to hit the problem, you could try adding something like
>> 
>> if (fsplan->scan.scanrelid == 0 && outerPlanState(node) == NULL &&
>> (estate->es_plannedstmt->commandType != CMD_SELECT ||
>> estate->es_rowMarks))
>> elog(WARNING, "foreign join plan lacks EPQ support");
>> 
>> near the beginning of postgresBeginForeignScan and then running your app
>> on a test server.

> Hmm, is there a reason this cannot be included as a sanity check always?

That's off-the-cuff rather than something I'm sure is correct.  But
yeah, I was wondering about pushing something like that into the
standard code.
        regards, tom lane


-- 
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

pgsql-bugs by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: [BUGS] BUG #14781: server process was terminated by signal 11:Segmentation fault
Next
From: "Ali ."
Date:
Subject: [BUGS] User who created a trigger is not able to drop it