| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | pgsql-committers(at)postgresql(dot)org |
| Subject: | pgsql: Fix two issues in plpython's handling of composite results. |
| Date: | 2011-08-17 21:33:10 |
| Message-ID: | E1Qtnja-0002ef-7U@gemulon.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Fix two issues in plpython's handling of composite results.
Dropped columns within a composite type were not handled correctly.
Also, we did not check for whether a composite result type had changed
since we cached the information about it.
Jan Urbański, per a bug report from Jean-Baptiste Quenot
Branch
------
master
Details
-------
http://git.postgresql.org/pg/commitdiff/2dada0cc85ee36f4e2b32a0463cb75ad9466589a
Modified Files
--------------
src/pl/plpython/expected/plpython_record.out | 21 +++++
src/pl/plpython/plpython.c | 114 +++++++++++++++++++-------
src/pl/plpython/sql/plpython_record.sql | 15 ++++
3 files changed, 120 insertions(+), 30 deletions(-)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-08-18 00:18:39 | pgsql: Update 9.1 release notes to reflect commits through today. |
| Previous Message | Andrew Dunstan | 2011-08-17 21:17:02 | Re: pgsql: Properly handle empty arrays returned from plperl functions. |