Re: problem with volatile functions in subselects ?

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Jaime Casanova <systemguards(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: problem with volatile functions in subselects ?
Date: 2006-09-02 20:57:27
Message-ID: 200609022057.k82KvRa02352@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
> "Jaime Casanova" <systemguards(at)gmail(dot)com> writes:
> >>> There's been some talk about prohibiting flattening if there are any
> >>> volatile functions in the subselect's targetlist, but nothing's been
> >>> done about that.
>
> > BTW, can you think in a good name for a GUC for this?
>
> I'm not in favor of a GUC for this; we should either do it or not.
>
> If we do it, basically the response to anyone who complains about loss
> of performance should be "fix your function to be marked stable or
> immutable, as appropriate".

Agreed. Are we doing this, or is it a TODO?

--
Bruce Momjian bruce(at)momjian(dot)us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2006-09-02 21:16:23 Re: Concurrent connections in psql patch
Previous Message Bruce Momjian 2006-09-02 20:55:19 Re: [HACKERS] extension for sql update