Re: Trigger function volatility

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Tyler Mitchell <fission(at)ldx(dot)ca>
Cc: pgsql-novice(at)postgresql(dot)org
Subject: Re: Trigger function volatility
Date: 2009-08-05 01:09:36
Message-ID: 25804.1249434576@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-novice

Tyler Mitchell <fission(at)ldx(dot)ca> writes:
> Can anyone think of any issues with IMMUTABLE in this case?

It's incorrect. The function is altering NEW, so I hardly see how you
can think it's immutable --- it has side effects.

The system might let you do this at the moment, because it pays
hardly any attention to the volatility classification of a trigger
function anyhow; but that doesn't make it a good idea.

regards, tom lane

In response to

Browse pgsql-novice by date

  From Date Subject
Next Message Tom Lane 2009-08-05 01:12:52 Re: can long-lived transactions cause problems?
Previous Message Lennin Caro 2009-08-05 00:26:49 Re: Graphical user interface