Re: Consistent segfault in complex query

From: Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Kyle Samson <kysamson(at)tripadvisor(dot)com>, "pgsql-hackers\(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Matthew Kelly <mkelly(at)tripadvisor(dot)com>
Subject: Re: Consistent segfault in complex query
Date: 2018-09-12 16:43:18
Message-ID: 87zhwmoehf.fsf@news-spur.riddles.org.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>>>>> "Andrew" == Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> writes:

Andrew> Going to see if this can be narrowed down further.

Simpler testcase, removing the CTE, so this is clearly just about
InitPlan:

create table mytable (flag boolean default false, foo integer);
insert into mytable default values;

session B:
begin; update mytable set flag = true;

session A:
update mytable set foo = case when not flag then foo else length((select 'foo')) end;

commit in B and watch A die in:
#1 0x0000000000b001bd in text_length (str=0) at varlena.c:647

--
Andrew (irc:RhodiumToad)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Banck 2018-09-12 17:12:20 Re: [HACKERS] Exclude schema during pg_restore
Previous Message Andrew Gierth 2018-09-12 16:33:22 Re: Consistent segfault in complex query