| From: | Takahiro Itagaki <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp> |
|---|---|
| To: | "Tatsuo Ishii" <ishii(at)postgresql(dot)org> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [SPAM]function side effects |
| Date: | 2010-02-23 04:15:15 |
| Message-ID: | 20100223131515.A177.52131E4D@oss.ntt.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Tatsuo Ishii" <ishii(at)postgresql(dot)org> wrote:
> VOLATILE functions such as random() and timeofday() apparently do not
> write and sending those queries that include such functions is
> overkill.
> Can we VOLATILE property divide into two categories, say, VOLATILE
> without write, and VOLATILE with write?
I think it's possible. We might borrow words and semantics from
unctional programming languages for functions with side effects.
How do they handle the issue?
BTW, random() *writes* the random seed, though no one will mind it.
Regards,
---
Takahiro Itagaki
NTT Open Source Software Center
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2010-02-23 04:44:40 | recovery.conf.sample |
| Previous Message | Jaime Casanova | 2010-02-23 04:00:31 | synchronous commit in dump |