pgsql: Fix plpython's overoptimistic caching of information about the - Mailing list pgsql-committers

From tgl@postgresql.org (Tom Lane)
Subject pgsql: Fix plpython's overoptimistic caching of information about the
Date
Msg-id 20080102031027.D8D8A7540F0@cvs.postgresql.org
Whole thread Raw
List pgsql-committers
Log Message:
-----------
Fix plpython's overoptimistic caching of information about the rowtype of
a trigger's target table.  The rowtype could change from one call to the
next, so cope in such cases, while avoiding doing repetitive catalog lookups.
Per bug #3847 from Mark Reid.

Backpatch to 8.2.x.  Likely this fix should go further back, but I can't test
it because I no longer have a machine with a pre-2.5 Python installation.
(Maybe we should rethink that idea about not supporting Python 2.5 in the
older branches.)

Modified Files:
--------------
    pgsql/src/pl/plpython:
        plpython.c (r1.105 -> r1.106)
        (http://developer.postgresql.org/cvsweb.cgi/pgsql/src/pl/plpython/plpython.c?r1=1.105&r2=1.106)

pgsql-committers by date:

Previous
From: tgl@postgresql.org (Tom Lane)
Date:
Subject: pgsql: Fix plpython's overoptimistic caching of information about the
Next
From: mkz@pgfoundry.org (User Mkz)
Date:
Subject: plproxy - plproxy: put 8.2 check into main plproxy.h to avoid random