Re: Query plans for plpgsql triggers

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Eric B(dot) Ridge" <ebr(at)tcdi(dot)com>
Cc: Postgresql <pgsql-general(at)postgresql(dot)org>
Subject: Re: Query plans for plpgsql triggers
Date: 2006-03-25 05:24:04
Message-ID: 14774.1143264244@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"Eric B. Ridge" <ebr(at)tcdi(dot)com> writes:
> I should have mentioned that while the UPDATE statement in the
> trigger function really is as simple as the above, "some_other_table"
> is actually a view with the requisite ON UPDATE DO INSTEAD rule:

This is the sort of detail that you really should not omit.

If you were using something newer than 7.4 then I'd ask for a complete
test case so I could look into improving the behavior --- but as it is,
I'd first suggest upgrading and seeing if the problem is already fixed.

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Eric B. Ridge 2006-03-25 05:46:49 Re: Query plans for plpgsql triggers
Previous Message Eric B. Ridge 2006-03-25 05:10:40 Re: Query plans for plpgsql triggers