Re: segfault due to invalid cached plan

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Nicolas Thauvin <nicolas(dot)thauvin(at)dalibo(dot)com>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: segfault due to invalid cached plan
Date: 2018-03-28 14:39:02
Message-ID: 20817.1522247942@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Nicolas Thauvin <nicolas(dot)thauvin(at)dalibo(dot)com> writes:
> A customer sent us a core dump of the crash of the background worker of
> the powa extension, running on 9.6.8 along side with cstore_fdw.
> The background worker loops on a plpgsql function, which then execute
> another plpgsql function that issues the query "TRUNCATE
> powa_statements_history_current".

I think the odds are very high that this is a cstore_fdw bug. The
core backend simply doesn't do anything very interesting with TRUNCATE.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2018-03-28 14:50:41 Re: [HACKERS] PATCH: multivariate histograms and MCV lists
Previous Message Dmitry Ivanov 2018-03-28 14:19:27 Re: [HACKERS] GSoC 2017: weekly progress reports (week 6)