From: | Stephan Szabo <sszabo(at)megazone23(dot)bigpanda(dot)com> |
---|---|
To: | Ron Snyder <snyder(at)roguewave(dot)com> |
Cc: | "'pgsql-general(at)postgresql(dot)org'" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Unexplainable slow down... |
Date: | 2002-03-14 15:37:54 |
Message-ID: | 20020314073518.G433-100000@megazone23.bigpanda.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, 13 Mar 2002, Ron Snyder wrote:
>
>
> > -----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.)
set enable_seqscan=off;
should do it.
> > 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.
What does pg_indexes show for them (it'll get back a human readable index
statement).
From | Date | Subject | |
---|---|---|---|
Next Message | Doug McNaught | 2002-03-14 15:40:28 | Re: User permissions |
Previous Message | John Gray | 2002-03-14 15:35:10 | Re: order by a XML column |