Quick Links

re: BUG #14053: postgres crashes in plpgsql under load of concurrent transactions

From:	Ranier Vilela <ranier(dot)vf(at)gmail(dot)com>
To:	PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Cc:	maxim(at)jeslalabs(dot)com
Subject:	re: BUG #14053: postgres crashes in plpgsql under load of concurrent transactions
Date:	2020-06-18 20:00:05
Message-ID:	CAEudQAoPULd5L7XR_EL1XPAW6ezTewfV02HRHm2vovxVm=wcSg@mail.gmail.com
Views:	Raw Message \| Whole Thread \| Download mbox \| Resend email
Thread:
Lists:	pgsql-hackers

Hi Maxim,

Coverity show that trap (1), still persists, even in HEAD.
CID 1425439 (#1 of 1): Explicit null dereferenced (FORWARD_NULL)
15. var_deref_model: Passing null pointer expr->expr_simple_state to
ExecEvalExpr, which dereferences it. [show details
<https://scan6.coverity.com/eventId=30547522-25&modelId=30547522-1&fileInstanceId=101889282&filePath=%2Fdll%2Fpostgres%2Fsrc%2Finclude%2Fexecutor%2Fexecutor.h&fileStart=290&fileEnd=295>]

Is really, it is very difficult to provide a minimum reproducible test case?
I tried, without success.

regards,
Ranier Vilela

	From	Date	Subject
Next Message	Tom Lane	2020-06-18 20:28:33	Re: More tzdb fun: POSIXRULES is being deprecated upstream
Previous Message	Alexey Kondratov	2020-06-18 18:46:28	Re: Physical replication slot advance is not persistent