Re: BUG #14781: server process was terminated by signal 11: Segmentation fault

Thank you for your answer so quickly.

>(gdb) p debug_query_string
>$1 = 0x2c2e748 "DO $$DECLARE\nBEGIN\n PERFORM dwh.load_trade_record_inc();\nEND$$;"

We added logging to the function and found out that the error always occurs on the same update
(in attachments)
Plan explain verbose in attachments

MAKSIM KARABA
Senior Systems Engineer, EPAM
Office: +375 17 389 0100 x 53194 Cell: +375296772871 Email: maksim_karaba(at)epam(dot)com
Minsk, Belarus (GMT+3) epam.com

-----Original Message-----
From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
Sent: Wednesday, August 16, 2017 4:47 PM
To: Maksim Karaba <Maksim_Karaba(at)epam(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: [BUGS] BUG #14781: server process was terminated by signal 11: Segmentation fault

maksim_karaba(at)epam(dot)com writes:
> We are getting error "server process was terminated by signal 11:
> Segmentation fault" and server goes to recovery mode on production system.
> It repeats several times a day, always on complicated updates using
> postgres_fdw.

Please show the failing query or queries. (If you don't have postmaster logs showing them, "p debug_query_string" in the core files should get the info.) Also, please show EXPLAIN VERBOSE plans for the query(s), as well as schema information (psql \d output would do) for the referenced tables.

https://wiki.postgresql.org/wiki/Guide_to_reporting_problems

regards, tom lane