| From: | Tomasz Myrta <jasiek(at)klaster(dot)net> |
|---|---|
| To: | alvarezp(at)alvarezp(dot)ods(dot)org, Lista dyskusyjna pgsql-sql <pgsql-sql(at)postgresql(dot)org> |
| Subject: | Re: [PERFORM] Seq scan on zero-parameters function |
| Date: | 2004-02-06 08:55:26 |
| Message-ID: | 4023567E.1020406@klaster.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance pgsql-sql |
Dnia 2004-02-06 09:43, Użytkownik Octavio Alvarez napisał:
> Thanks for the hint.
>
> In fact, my current_period_id() is based on time, but it should be
> constant along the query execution. I mean, I don't want some records
> filtered with some values and other with other values... I'll have an
> uncongruent recordset.
Well - you didn't read the chapter I noticed you, did you?
Look at function now(). It returns always the same value inside
transaction. If your current_period_id() works the same way as now()
then declare it as STABLE.
Regards,
Tomasz Myrta
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruno BAGUETTE | 2004-02-06 08:58:44 | Increase performance of a UNION query that thakes 655.07 msec to be runned ? |
| Previous Message | Richard Huxton | 2004-02-06 08:50:50 | Re: Seq scan on zero-parameters function |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | jan bok | 2004-02-06 11:33:00 | unsubscribe |
| Previous Message | Richard Huxton | 2004-02-06 08:50:50 | Re: Seq scan on zero-parameters function |