From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | andreas(dot)zeugswetter(at)telecom(dot)at (Zeugswetter Andreas) |
Cc: | pgsql-hackers(at)hub(dot)org |
Subject: | Re: [HACKERS] indexing words slow |
Date: | 1998-03-11 19:05:17 |
Message-ID: | 199803111905.OAA21827@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
>
> > On the other hand, if I do a count(*) on '^ric', his takes consequently
> > around 1:30 mins, no matter how often I run it. This returns 7866.
> >
> > A search on count(*) of '^lling' and '^tones' takes around 2.5 secs after
> > running it several times.
>
> Since postgres will still read the data row (even for this count(*)) I would guess,
> that this is a data distribution problem. Maybe you could cluster your data ?
> Maybe the '^rol' rows stick pretty much together, whilst the '^ric' rows
> are evenly distributed on all datapages. Of course there would be room
> for improvement if postgresql would not read the data pages, which are not needed
> for any query that only selects columns that are part of the index.
>
Brilliant. I had forgotten that the data pages are accessed as well as
the index pages. The CLUSTER command works in 6.3, so perhaps that will
change some times.
--
Bruce Momjian | 830 Blythe Avenue
maillist(at)candle(dot)pha(dot)pa(dot)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)
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 1998-03-11 19:08:04 | Re: AW: [HACKERS] attlen weirdness? |
Previous Message | Bruce Momjian | 1998-03-11 18:50:13 | Re: AW: [HACKERS] varchar() vs char16 performance |