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-11 17:59:46 |
Message-ID: | 3EE727C2.29810.B1B21EE@localhost |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
> There is a known bug with applying the same plpython trigger function to
> multiple tables that have different rowtypes --- the rowtype info gets
> cached for the first table the function is used with in a session, and
> then inappropriately reused with the other tables. Does this seem to
> describe your observations?
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. Another thing that seems weird about it is that the
value is sometimes 1 and sometimes 0. In my test case, it's 1 when
the value should be 'test', and 0 when '1234'.
Had I not noticed plpython's problem with char fields, I would have
already run smack into the caching problem you described. :-(
--
Arthur Ward
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-06-11 18:38:44 | Re: 7.3.3 - plpython & trigger problem |
Previous Message | Tom Lane | 2003-06-11 17:34:23 | Re: 7.3.3 - plpython & trigger problem |