| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Cc: | "Zeugswetter Andreas ADI SD" <ZeugswetterA(at)spardat(dot)at>, "Jim C(dot) Nasby" <jim(at)nasby(dot)net>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: [HACKERS] Hints proposal |
| Date: | 2006-10-13 22:59:17 |
| Message-ID: | 200610131559.18328.josh@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-performance |
Andreas,
> I think we need to more precisely define the problems of our system with
> point in time statistics
>
> -- no reaction to degree of other concurrent activity
> -- no way to react to abnormal skew that only persists for a very short
> duration
> -- too late reaction to changing distribution (e.g. current date column
> when a new year starts)
> and the variant: too late adaption when a table is beeing filled
> -- missing cost/selectivity estimates for several parts of the system
How would we manage point-in-time statistics? How would we collect them &
store them? I think this is an interesting idea, but very, very hard to
do ...
--
--Josh
Josh Berkus
PostgreSQL @ Sun
San Francisco
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2006-10-13 23:34:32 | Re: [PERFORM] Hints proposal |
| Previous Message | Josh Berkus | 2006-10-13 22:57:23 | Re: [HACKERS] Hints proposal |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Josh Berkus | 2006-10-13 23:34:32 | Re: [PERFORM] Hints proposal |
| Previous Message | Josh Berkus | 2006-10-13 22:57:23 | Re: [HACKERS] Hints proposal |