| From: | PFC <lists(at)boutiquenumerique(dot)com> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Alvaro Herrera" <alvherre(at)dcc(dot)uchile(dot)cl> |
| Cc: | "Josh Berkus" <josh(at)agliodbs(dot)com>, "Michael Fuhr" <mike(at)fuhr(dot)org>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Functionscan estimates |
| Date: | 2005-04-09 11:29:10 |
| Message-ID: | op.soyp6wpeth1vuj@localhost |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-performance |
> But with all due respect to Joe, I think the reason that stuff got
> trimmed is that it didn't work very well. In most cases it's
> *hard* to write an estimator for a SRF. Let's see you produce
> one for dblink() for instance ...
Good one...
Well in some cases it'll be impossible, but suppose I have a function
get_id_for_something() which just grabs an ID using dblink, then I know it
returns one row, and pg would be interested in that information too !
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John DeSoi | 2005-04-09 14:03:35 | table and column information from cursor? |
| Previous Message | PFC | 2005-04-09 11:25:47 | Re: Functionscan estimates |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | BarryS | 2005-04-09 13:19:12 | Re: Postgresql vs SQLserver for this application ? |
| Previous Message | PFC | 2005-04-09 11:25:47 | Re: Functionscan estimates |