| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Oliver Jowett <oliver(at)opencloud(dot)com> |
| Cc: | Bruno Wolff III <bruno(at)wolff(dot)to>, Gaetano Mendola <mendola(at)bigfoot(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Stable function semantics (was Re: Mislabeled timestamp functions) |
| Date: | 2004-10-03 21:27:25 |
| Message-ID: | 7887.1096838845@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-novice pgsql-sql |
Oliver Jowett <oliver(at)opencloud(dot)com> writes:
> Bruno Wolff III wrote:
>> I should have said within a single statement instead of within a single
>> transaction.
> As I understand Tom's earlier explanation of this, the definition is
> even more narrow: stable functions only need to return the same value
> across a single tablescan.
> It might be useful to have some variant of stable (or perhaps just a
> change in semantics) such that the function returns the same value for
> identical parameters until the next CommandCounterIncrement.
In practice I think these are equivalent definitions.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2004-10-03 21:38:46 | Re: AIX and V8 beta 3 |
| Previous Message | Oleg Bartunov | 2004-10-03 20:51:47 | Re: [HACKERS] slow count() was: tsearch2 poor performance |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2004-10-03 21:49:32 | Re: Mislabeled timestamp functions (was Re: [SQL] [NOVICE] date_trunc'd timestamp index possible?) |
| Previous Message | Vitaly Belman | 2004-10-03 18:05:56 | Re: Writing plpgsql not in a function (directly from plsql)? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Greg Stark | 2004-10-03 21:49:32 | Re: Mislabeled timestamp functions (was Re: [SQL] [NOVICE] date_trunc'd timestamp index possible?) |
| Previous Message | Jens Arnfelt | 2004-10-03 20:50:13 | How to convert 3 colums to timestamp with timezone |