| From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | jwieck(at)debis(dot)com |
| Cc: | andreas(dot)zeugswetter(at)telecom(dot)at, jwieck(at)debis(dot)com, hackers(at)postgreSQL(dot)org |
| Subject: | Re: [HACKERS] Re: order by and index path |
| Date: | 1998-10-15 16:04:42 |
| Message-ID: | 199810151604.MAA15195@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> could return at max 8999 tuples and
>
> WHERE key > 50 AND key < 70
>
> has a maximum of 998 result tuples. This would be the
> information required to make the right decision for the case
> where all rows selected are wanted.
>
> We do not have this statistical information. So the whole
> thing is at this time academic.
But we do have statistical information in pg_statistic if you run vacuum
analyze.
--
Bruce Momjian | http://www.op.net/~candle
maillist(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 1998-10-15 16:06:04 | Re: [HACKERS] PostgreSQL v6.4 BETA2... |
| Previous Message | Oleg Bartunov | 1998-10-15 16:01:23 | Re: [HACKERS] What about LIMIT in SELECT ? |