Re: Strange RETURN NEXT behaviour in Postgres 8.0 - Mailing list pgsql-hackers

From Christopher Kings-Lynne
Subject Re: Strange RETURN NEXT behaviour in Postgres 8.0
Date
Msg-id 421460CE.60001@familyhealth.com.au
Whole thread Raw
In response to Re: Strange RETURN NEXT behaviour in Postgres 8.0  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
> It looks like the code that handles returning a RECORD variable doesn't
> cope with dropped columns in the function result rowtype.
> 
> (If you instead declare rec as usno%rowtype, you get a different set
> of misbehaviors after adding/dropping columns, so that code path isn't
> perfect either :-()

Isn't it amazing, Tom, that that column dropping code that we did up for 
7.3 is STILL causing bugs :D

Chris


pgsql-hackers by date:

Previous
From: Christopher Kings-Lynne
Date:
Subject: Re: Help me recovering data
Next
From: "John Hansen"
Date:
Subject: Re: Terminating a SETOF function call sequence