| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
| Cc: | Denis Feklushkin <denis(dot)feklushkin(at)gmail(dot)com>, pgsql-bugs <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: [Fwd: ERROR: cannot extract system attribute from minimal tuple] |
| Date: | 2011-02-10 03:37:36 |
| Message-ID: | 9888.1297309056@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Alvaro Herrera <alvherre(at)commandprompt(dot)com> writes:
> Hmm, yeah, in an assert-enabled build of HEAD it dies with:
> TRAP: FailedAssertion(!(attno > 0), Archivo: /pgsql/source/HEAD/src/backend/executor/execJunk.c, Lnea: 251)
> I don't have time to track this down right now ...
It's a shortcoming in the PlanRowMark+resjunk column data structure:
when we flatten subqueries, the rangetable indexes of the relations
to be row-locked can change, but the resjunk column names already
assigned to represent their ctid's aren't updated. Working on a
fix now.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-02-10 03:58:46 | Re: possible bug: orphaned files left after immediate shutdown during DDL |
| Previous Message | Jeff Davis | 2011-02-10 03:37:06 | possible bug: orphaned files left after immediate shutdown during DDL |