Re: Trigger Crashes Database Back End.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Childs <blue(dot)dragon(at)blueyonder(dot)co(dot)uk>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: Trigger Crashes Database Back End.
Date: 2003-02-19 16:18:19
Message-ID: 11855.1045671499@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Peter Childs <blue(dot)dragon(at)blueyonder(dot)co(dot)uk> writes:
> This only happerns when you have the following trigger (at bottom) on the
> database. The trigger is attached to pratically every table.

The plpython trigger support fails if the same trigger is attached to
more than one table (unless the tables all have identical rowtypes).
This was only realized last week sometime. We've been promised a patch
soon.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Robert Haas 2003-02-19 20:29:42 setting time zone during a transaction causes time warp
Previous Message Peter Childs 2003-02-19 15:33:14 Trigger Crashes Database Back End.