| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Олег Самойлов <splarv(at)ya(dot)ru> |
| Cc: | "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: stable for each row before insert trigger |
| Date: | 2019-10-18 07:15:58 |
| Message-ID: | 27662.1571382958@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
=?utf-8?B?0J7Qu9C10LMg0KHQsNC80L7QudC70L7Qsg==?= <splarv(at)ya(dot)ru> writes:
> According to documentation the words "VOLATILE, STABLE, IMMUTABLE" is somehow useful with trigger functions, for instance mentioned that the AFTER INSERT trigger should be VOLATILE. The question is how this words affect a for each row before insert trigger? Can be some optimisation here?
Where did you read that? There's no optimization that considers the
volatility of trigger functions --- they'll be called exactly when
specified, no more or less.
There are some PLs that might behave differently depending on whether they
think the function is volatile or not, but that's independent of whether
the function is a trigger.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Luca Ferrari | 2019-10-18 08:09:12 | Re: stable for each row before insert trigger |
| Previous Message | Andreas Kretschmer | 2019-10-18 07:08:17 | Re: Postgres Point in time Recovery (PITR), |