Re: avoid pulling up subquerys that contain volatile functions?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jaime Casanova <systemguards(at)gmail(dot)com>
Cc: PG Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: avoid pulling up subquerys that contain volatile functions?
Date: 2005-10-08 18:10:00
Message-ID: 29438.1128795000@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Jaime Casanova <systemguards(at)gmail(dot)com> writes:
> but this example seems to clarify (or at least i think) that we have to avoid
> pulling up subquerys containing volatile functions:

This is exactly the same example discussed in previous threads on this
issue. Do you think it will change anyone's mind?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2005-10-08 19:36:01 Re: [HACKERS] Kerberos brokenness and oops question in 8.1beta2
Previous Message Alvaro Herrera 2005-10-08 17:16:34 Re: Issue is changing _bt_compare function and