From: | Ron Snyder <snyder(at)roguewave(dot)com> |
---|---|
To: | 'Stephan Szabo' <sszabo(at)megazone23(dot)bigpanda(dot)com> |
Cc: | "'pgsql-general(at)postgresql(dot)org'" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Unexplainable slow down... |
Date: | 2002-03-14 06:59:10 |
Message-ID: | F888C30C3021D411B9DA00B0D0209BE8026E2DB2@cvo-exchange.cvo.roguewave.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> -----Original Message-----
> From: Stephan Szabo [mailto:sszabo(at)megazone23(dot)bigpanda(dot)com]
> > Limit (cost=0.00..833.71 rows=15 width=426)
> > -> Seq Scan on builds (cost=0.00..123873.38 rows=2229 width=426)
> >
> > EXPLAIN
>
> What's the explain for limit 14? And what if you set
> enable_seqscan=off?
The explain for limit 14 was the same (except that rows=14). I know I can
disable seqscan in the .conf file-- is there a way that I can turn that off
in the psql client? (It's a production database and they (the users) have
about 300 client connections that don't handle disconnections very well.)
We did increase shared_buffers from 1024 to 8096, but it doesn't seem to
have helped.
>
> Some of these indices seem obvious others I'm not sure what
> they're supposed to cover.
>
I agree, unfortunately I don't have a lot of information about the indices.
Thanks for taking a look.
-ron
From | Date | Subject | |
---|---|---|---|
Next Message | Martijn van Oosterhout | 2002-03-14 07:06:33 | Re: Last Insert |
Previous Message | Oliver Elphick | 2002-03-14 06:36:32 | Re: Postgres on Apple hardware? |