| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Josh Berkus <josh(at)agliodbs(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Alpha 1 release notes |
| Date: | 2009-08-17 19:52:20 |
| Message-ID: | 6658.1250538740@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Josh Berkus <josh(at)agliodbs(dot)com> writes:
> Also, does the ADD/DROP COLUMN plpgsql patch fix any cases other than
> RETURNS QUERY? I can't tell from the patch.
Yes, I believe it does, but hadn't bothered to work up any test cases.
The places it touched in plpgsql are
* returning a single composite value
* returning a tuple from a trigger function
* assignment to a record variable
* RETURN QUERY
I think that the trigger function case would usually work (since you'd
generally be doing RETURN NEW or RETURN OLD which should have dead
columns in the right places already) but the other two were probably
just as problematic as RETURN QUERY.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2009-08-17 20:26:41 | Re: Alpha 1 release notes |
| Previous Message | Tom Lane | 2009-08-17 19:42:38 | Re: Another try at reducing repeated detoast work for PostGIS |