On Monday, Oct 13, 2003, at 21:24 Pacific/Honolulu, mila wrote:
Seth,
My system: RH9, PG 7.3.4, IDE, 1 gig RAM, celeron 1.7
...
Size of table: 16212 rows
Params: shared_buffers = 128, effective_cache_size = 8192
Just in case,
the "shared_buffers" value looks a bit far too small for your system.
I
Hello,
Thanks to all the previous suggestions for my previous question. I've
done a lot more research and playing around since then, and luckily I
think I have a better understanding of postgresql.
I still have some queries that don't use an index, and I was wondering
if there were some ot
Is there any way to speed this up, or is that DISTINCT going to keep
hounding me?
I checked the mailing list, and didn't see anything like this.
Any tips or hints would be greatly appreciated. Thanks for your help!
Seth
Try group by instead. I think this is an old bug its fixed in
7.3.2
Hello,
I am running 7.3.2 RPMs on RH9, on a celeron 1.7 w/ 1gig ram.
I have a table that has 6.9 million rows, 2 columns, and an index on
each column. When I run:
SELECT DISTINCT column1 FROM table
It is very, very slow (10-15 min to complete). An EXPLAIN shows no
indexes are being used.
I
