From: | Filip Rembiałkowski <plk(dot)zuber(at)gmail(dot)com> |
---|---|
To: | "Vincenzo Romano" <vincenzo(dot)romano(at)gmail(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: stable functions |
Date: | 2007-05-31 12:06:33 |
Message-ID: | 92869e660705310506j583eb163if315b1edefa9a01f@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
2007/5/31, Vincenzo Romano <vincenzo(dot)romano(at)gmail(dot)com>:
> Nonetheless your remark makes a lot of sense and I'm still in dubt.
> In my case the "creatorfunc" has no parameters and returns void as it reads
> data from configuration tables.
> And it should be OK if ti were run only once.
AFAIK, the only practical sense of defining functions as
stable/immutable is the runtime query optimization.
If you don't need any optimization, and the function takes no params,
why not leave it as volatile?
> I'd say that some more explaination in the documentatio would be great under
> "33.6. Function Volatility Categories".
For me it's clear enough.
--
Filip Rembiałkowski
From | Date | Subject | |
---|---|---|---|
Next Message | Bhavana.Rakesh | 2007-05-31 12:57:41 | Re: jdbc pg_hba.conf error |
Previous Message | Erwin Brandstetter | 2007-05-31 11:52:11 | Re: SELECT <all fields except "bad_field"> from mytbl; |