Re: Stored procedure declared as VOLATILE => no good optimization is done - Mailing list pgsql-performance

From Tom Lane
Subject Re: Stored procedure declared as VOLATILE => no good optimization is done
Date
Msg-id 26735.1287196294@sss.pgh.pa.us
Whole thread Raw
In response to Re: Stored procedure declared as VOLATILE => no good optimization is done  (Tatsuo Ishii <ishii@postgresql.org>)
Responses Re: Stored procedure declared as VOLATILE => no good optimization is done  (Merlin Moncure <mmoncure@gmail.com>)
List pgsql-performance
Tatsuo Ishii <ishii@postgresql.org> writes:
> So can I say "if a function is marked IMMUTABLE, then it should never
> modify database"? Is there any counter example?
> It seems if above is correct, I can say STABLE functions should never
> modify databases as well.

Both of those things are explicitly stated here:
http://developer.postgresql.org/pgdocs/postgres/xfunc-volatility.html

            regards, tom lane

pgsql-performance by date:

Previous
From: Navkirat Singh
Date:
Subject: UUID performance as primary key
Next
From: Craig Ringer
Date:
Subject: Re: UUID performance as primary key