| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Maksim Karaba <Maksim_Karaba(at)epam(dot)com>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #14781: server process was terminated by signal 11: Segmentation fault |
| Date: | 2017-08-16 16:56:49 |
| Message-ID: | 28874.1502902609@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Alvaro Herrera <alvherre(at)2ndquadrant(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ali . | 2017-08-16 21:46:21 | User who created a trigger is not able to drop it |
| Previous Message | Alvaro Herrera | 2017-08-16 16:47:37 | Re: BUG #14781: server process was terminated by signal 11: Segmentation fault |