pgsql: Fix two issues in plpython's handling of composite results. - Mailing list pgsql-committers

From Tom Lane
Subject pgsql: Fix two issues in plpython's handling of composite results.
Date
Msg-id E1Qtnja-0002ef-7U@gemulon.postgresql.org
Whole thread Raw
List 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(-)


pgsql-committers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: pgsql: Properly handle empty arrays returned from plperl functions.
Next
From: Tom Lane
Date:
Subject: pgsql: Update 9.1 release notes to reflect commits through today.