| From: | Jaime Casanova <jcasanov(at)systemguards(dot)com(dot)ec> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Tatsuo Ishii <ishii(at)postgresql(dot)org>, gsstark(at)mit(dot)edu, Kevin(dot)Grittner(at)wicourts(dot)gov, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: function side effects |
| Date: | 2010-02-24 03:46:13 |
| Message-ID: | 3073cc9b1002231946l7d2f2861r3760a4412043c04@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Feb 23, 2010 at 10:18 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Personally I find that goal rather suspect anyway.
> I think the chances of determining this reliably in pgpool are
> negligible, even if functions were marked like that. You would need to
> duplicate *all* of the backend's parsing and all of its state (eg schema
> search path) in order to discover anything.
>
i agree with that, as Alvaro suggested maybe a way to ask the server
about the whole query is the way to go
--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ecuador
Cel. +59387171157
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fujii Masao | 2010-02-24 04:58:35 | Re: Re: [COMMITTERS] pgsql: Move documentation of all recovery.conf option to a new chapter. |
| Previous Message | Bruce Momjian | 2010-02-24 03:33:49 | pgsql: Remove pre-7.4 documentaiton mentions, now that 8.0 is the oldest |