| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Greg Stark <gsstark(at)mit(dot)edu> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Idea about estimating selectivity for single-column expressions |
| Date: | 2009-08-19 14:30:45 |
| Message-ID: | 21371.1250692245@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Greg Stark <gsstark(at)mit(dot)edu> writes:
> We could add another flag in pg_proc for functions which cannot throw
> an error. Perhaps all index operator class operators be required to
> use such functions too?
It would be an extremely small set. For starters, anything that returns
a pass-by-reference data type would be out automatically --- the palloc
to return the result could hit out-of-memory.
Now maybe we could define the flag as meaning "if this does throw an
error it's okay for the calling query to fail too", which I think is
reasonable for out-of-memory type errors. But it's getting pretty
squishy at that point, and I think we'd have a lot of problems with
mislabeled functions.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2009-08-19 15:16:49 | Re: FDW-based dblink (WIP) |
| Previous Message | Greg Stark | 2009-08-19 14:28:44 | Re: Idea about estimating selectivity for single-column expressions |