Re: Strange RETURN NEXT behaviour in Postgres 8.0

From: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Richard Huxton <dev(at)archonet(dot)com>, "Sergey E(dot) Koposov" <math(at)sai(dot)msu(dot)ru>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Strange RETURN NEXT behaviour in Postgres 8.0
Date: 2005-02-17 09:15:58
Message-ID: 421460CE.60001@familyhealth.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message John Hansen 2005-02-17 09:40:07 Re: Terminating a SETOF function call sequence
Previous Message Thomas Hallgren 2005-02-17 09:14:05 Terminating a SETOF function call sequence