Re: 9.1rc1: TRAP: FailedAssertion("!(item_width > 0)", File: "costsize.c", Line: 3274) - Mailing list pgsql-hackers

From Tom Lane
Subject Re: 9.1rc1: TRAP: FailedAssertion("!(item_width > 0)", File: "costsize.c", Line: 3274)
Date
Msg-id 15075.1314069810@sss.pgh.pa.us
Whole thread Raw
In response to Re: 9.1rc1: TRAP: FailedAssertion("!(item_width > 0)", File: "costsize.c", Line: 3274)  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Robert Haas <robertmhaas@gmail.com> writes:
> On Mon, Aug 22, 2011 at 4:16 PM, Erik Rijkers <er@xs4all.nl> wrote:
>> The below SQL causes:
>> TRAP: FailedAssertion("!(item_width > 0)", File: "costsize.c", Line: 3274)

> I can reproduce this on master but not on 9.0.  I suspect the problem
> was introduced by this commit:
> commit 0f61d4dd1b4f95832dcd81c9688dac56fd6b5687

Well, that's a pretty safe bet considering the Assert is in code that
didn't exist before that commit ;-).  The question is why the per-column
width estimate hasn't been set for that column.  Looking at the
coredump, I see that the width *did* get set for the subquery's other
output column, which makes it even weirder.  Too tired to dig further
right now though.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Daniel Farina
Date:
Subject: Re: SSL-mode error reporting in libpq
Next
From: Greg Smith
Date:
Subject: Re: Displaying accumulated autovacuum cost