From: | Arthur Ward <ward005(at)bama(dot)ua(dot)edu> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: 7.3.3 - plpython & trigger problem |
Date: | 2003-06-12 01:52:39 |
Message-ID: | 3EE79697.12005.CCC15E8@localhost |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
> > No, it does not match what I'm seeing. To check, I dropped my test
> > table and function, exited psql, started psql, and ran the script I
> > originally posted. I still get the same results. If I had to guess, this
> > seems more like a Postgres to plpython conversion problem than a
> > caching problem.
>
> Bingo. The conversion-method-selection code is not only broken (for
> several datatypes besides this one), but quite wrongheaded (testing on
> the name of the datatype is the wrong approach). I've applied the
> attached patch; please confirm it works for you.
Applied successfully to 7.3.3 and the bug in question is fixed for my
situation. Thanks a bunch for the quick fix!
Now to implement the workaround for the plpython trigger &
rowtype caching problem...
--
Arthur Ward
From | Date | Subject | |
---|---|---|---|
PostgreSQL : | Zíka Aleš, Ing. | 2003-06-12 09:45:00 | PostgreSQL : returnType void가있는 SQL 롤 토토 |
Previous Message | Tom Lane | 2003-06-11 18:47:13 | Re: valgrind |