Re: CHECK problem really OK now... - Mailing list pgsql-sql

From Tom Lane
Subject Re: CHECK problem really OK now...
Date
Msg-id 6107.1001529418@sss.pgh.pa.us
Whole thread Raw
In response to CHECK problem really OK now...  (Kovacs Baldvin <kb136@hszk.bme.hu>)
List pgsql-sql
Kovacs Baldvin <kb136@hszk.bme.hu> writes:
> I tried, and it works: the current CVS version really runs
> happily the query what sent to heaven our 7.1 version of the
> backend.

I believe this traces to a fix I made in May:

2001-05-27 16:48  tgl
* src/: backend/executor/execJunk.c, backend/executor/execMain.c,include/executor/executor.h,
include/nodes/execnodes.h:When usinga junkfilter, the output tuple should NOT be stored back into thesame tuple slot
thatthe raw tuple came from, because that slot hasthe wrong tuple descriptor.  Store it into its own slot with
thecorrectdescriptor, instead.  This repairs problems with SPIfunctions seeing inappropriate tuple descriptors --- for
example,plpgsqlcode failing to cope with SELECT FOR UPDATE.
 

I didn't realize at the time that the error would also affect updates of
child tables, but tracing through your example with 7.1 shows clearly
that the CHECK is being applied to a slot that contains a four-column
tuple and only a three-column descriptor.  Ooops.
        regards, tom lane


pgsql-sql by date:

Previous
From: Frederick Klauschen
Date:
Subject: Query does not work: parse ERROR, Re: How to enter lists into database: Problems with solution.
Next
From: "Josh Berkus"
Date:
Subject: Re: Query does not work: parse ERROR, Re: How to enter lists into database: Problems with solution.