| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Volker Grabsch <vog(at)notjusthosting(dot)com>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Calculation of unused columns |
| Date: | 2009-10-19 17:48:58 |
| Message-ID: | 1255974538.492.21.camel@ebony |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On Mon, 2009-10-19 at 13:43 -0400, Tom Lane wrote:
> Simon Riggs <simon(at)2ndQuadrant(dot)com> writes:
> > On Sat, 2009-10-17 at 21:41 -0400, Tom Lane wrote:
> >> one thing we'd have to consider
> >> is whether it is okay to suppress calculation of columns containing
> >> volatile functions.
>
> > I think we should have a 4th class of functions,
> > volatile-without-side-effects (better name needed, obviously).
>
> What for? There wouldn't be that many, I think. random() and
> clock_timestamp(), yeah, but most volatile user-defined functions
> are either volatile-with-side-effects or misdeclared.
Read only vs. read write?
--
Simon Riggs www.2ndQuadrant.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gerhard Wiesinger | 2009-10-19 17:54:45 | Re: Calculation of unused columns |
| Previous Message | Kevin Grittner | 2009-10-19 17:48:42 | Re: Calculation of unused columns |