| From: | tgl(at)postgresql(dot)org (Tom Lane) |
|---|---|
| To: | pgsql-committers(at)postgresql(dot)org |
| Subject: | pgsql: Fix plpython's overoptimistic caching of information about the |
| Date: | 2008-01-02 03:10:34 |
| Message-ID: | 20080102031034.DB8247540F0@cvs.postgresql.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | 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.)
Tags:
----
REL8_2_STABLE
Modified Files:
--------------
pgsql/src/pl/plpython:
plpython.c (r1.90.2.3 -> r1.90.2.4)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/pl/plpython/plpython.c?r1=1.90.2.3&r2=1.90.2.4)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | User Mkz | 2008-01-02 09:31:58 | plproxy - plproxy: put 8.2 check into main plproxy.h to avoid random |
| Previous Message | Tom Lane | 2008-01-02 03:10:27 | pgsql: Fix plpython's overoptimistic caching of information about the |