Skip site navigation (1) Skip section navigation (2)

Re: BUG #5548: ERROR: invalid attnum ## for rangetable entry on EXPLAIN VERBOSE, not on EXPLAIN

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Daniel Grace <dgrace(at)wingsnw(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5548: ERROR: invalid attnum ## for rangetable entry on EXPLAIN VERBOSE, not on EXPLAIN
Date: 2010-07-09 21:15:34
Message-ID: 24976.1278710134@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
Daniel Grace <dgrace(at)wingsnw(dot)com> writes:
> Plan that fails on EXPLAIN VERBOSE:
> "Nested Loop  (cost=0.00..132.35 rows=24 width=4)"
> "  ->  Subquery Scan on t  (cost=0.00..131.00 rows=6 width=4)"
> "        Filter: (t.foo IS NULL)"
> "        ->  WindowAgg  (cost=0.00..119.50 rows=1150 width=4)"
> "              ->  Merge Join  (cost=0.00..102.25 rows=1150 width=4)"
> "                    Merge Cond: (acal.id = acal.id)"
> "                    ->  Index Scan using allocation_calendar_pkey on
> allocation_calendar acal  (cost=0.00..42.50 rows=1150 width=4)"
> "                    ->  Index Scan using allocation_calendar_pkey on
> allocation_calendar acal  (cost=0.00..42.50 rows=1150 width=4)"
> "  ->  Materialize  (cost=0.00..1.06 rows=4 width=0)"
> "        ->  Seq Scan on yearinfo yi  (cost=0.00..1.04 rows=4 width=0)"
> --> ERROR:  invalid attnum 2 for rangetable entry t

I've applied a patch for this; it'll be in 9.0beta4.  Thanks for the
report!

			regards, tom lane

In response to

pgsql-bugs by date

Next:From: Konstantin KulikovDate: 2010-07-12 07:16:03
Subject: BUG #5552: incorrect returned value of time
Previous:From: Robert HaasDate: 2010-07-09 19:49:58
Subject: Re: BUG #5539: Generally incorrect planner estimations on join with UNION ALL

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group