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

Re: backend crash with certain statements/tables

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jeff Bohmer <bohmer(at)visionlink(dot)org>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: backend crash with certain statements/tables
Date: 2004-03-02 17:46:11
Message-ID: 29901.1078249571@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
Jeff Bohmer <bohmer(at)visionlink(dot)org> writes:
> Running any of these statements on my database causes the backend to 
> crash (example from PG log below):

Crash confirmed here.  Seems to be a side-effect of the 7.4 optimization
that tries to avoid "unnecessary" projection steps.  In the "SELECT *
FROM foo LIMIT" case, the scan plan decides it need not do projection,
but actually one must occur (else heap_insert will scribble on the
source table :-().  The junkfilter code in execMain.c is supposed to
catch this situation, but it's fooled by the presence of a LIMIT step.
There may be some related cases, need to think more.

I should have a patch later today.

			regards, tom lane

In response to

Responses

pgsql-bugs by date

Next:From: Jeff BohmerDate: 2004-03-02 18:09:04
Subject: Re: backend crash with certain statements/tables
Previous:From: Jeff BohmerDate: 2004-03-02 16:22:56
Subject: backend crash with certain statements/tables

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