Re: [HACKERS] indexes and floats - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: [HACKERS] indexes and floats
Date
Msg-id 199808061541.LAA07831@candle.pha.pa.us
Whole thread Raw
In response to Re: [HACKERS] indexes and floats  (Vadim Mikheev <vadim@krs.ru>)
Responses Re: [HACKERS] indexes and floats  (Brook Milligan <brook@trillium.NMSU.Edu>)
List pgsql-hackers
> Thomas G. Lockhart wrote:
> >
> > > istm that we should be focusing on Vadim's hints on what it would take
> > > to use indices with function calls on constants...
> >
> > Looking at Vadim's note again, maybe it will be the parser's duty to
> > insert the PARAM_EXEC node; will need more details or some time to look
> > at it...
>
> Sorry, but maybe it would be better to add new attribute
> to pg_proc (and change CREATE FUNCTION syntax) to let
> parser know does result of function call on constants depend
> on execution time or not. This would be much better just
> execute function in parser and replace function with
> constant.
> Currently, only random(), now() and SPI-functions should be
> replaced by PARAM_EXEC, all others could be evaluated by parser.

I see.  We have pg_proc.proiscachable.  This looks like a good
candidate, and is not used for anything currently.  Maybe rename it to
something clearer.

--
Bruce Momjian                          |  830 Blythe Avenue
maillist@candle.pha.pa.us              |  Drexel Hill, Pennsylvania 19026
  +  If your life is a hard drive,     |  (610) 353-9879(w)
  +  Christ can be your backup.        |  (610) 853-3000(h)

pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: AW: [HACKERS] Large objects names
Next
From: Brook Milligan
Date:
Subject: Re: [HACKERS] indexes and floats