Re: BUG #3847: plpython trigger caches table structure - doesn't see new / changed columns

From: "Mark Reid" <reid(dot)write(at)gmail(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #3847: plpython trigger caches table structure - doesn't see new / changed columns
Date: 2008-01-02 18:11:32
Message-ID: 162057b00801021011l4403dbb6qbc514eee79c8f6a7@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

We've run our real-life test cases and they've all worked properly using
this patch too. Thanks again.
-Mark.

On Jan 1, 2008 8:07 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:

> "Mark Reid" <reid(dot)write(at)gmail(dot)com> writes:
> > The trigger function does not recognize the "test4" column the second
> time
> > it is added - the update throws an error.
>
> Try this patch:
> http://archives.postgresql.org/pgsql-committers/2008-01/msg00016.php
>
> regards, tom lane
>

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Peter Eisentraut 2008-01-02 19:40:00 Re: BUG #3822: Nonstandard precedence for comparison operators
Previous Message Mark Reid 2008-01-02 07:03:22 Re: BUG #3847: plpython trigger caches table structure - doesn't see new / changed columns