From: | "Mark A(dot) Summers" <msummers(at)irtnet(dot)com> |
---|---|
To: | pgsql-sql(at)postgresql(dot)org |
Subject: | Re: SQL Help |
Date: | 2001-01-29 16:29:02 |
Message-ID: | 9545t5$2bs0$1@news.tht.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
I am loser -- I didn't realize there was analyze option on vacuum -- I
created another index on Publisher code -- Now it smokes
thanks
Mark Summers
"Stephan Szabo" <sszabo(at)megazone23(dot)bigpanda(dot)com> wrote in message
news:Pine(dot)BSF(dot)4(dot)21(dot)0101261746560(dot)98620-100000(at)megazone23(dot)bigpanda(dot)com(dot)(dot)(dot)
>
> On Fri, 26 Jan 2001, Mark A. Summers wrote:
>
> > I am having trouble with the following query taking forever:
> > -----
> > SELECT * FROM ret108108_00, product
> > WHERE ret108108_00."isbn" = product."Item1"
> >
> > AND product."SuperCategory" = '1'
> > AND product."PublisherCode" = 'ZON'
> > ORDER BY ret108108_00.qty DESC LIMIT 100
> > ----
> > The problem is the second AND -- if I take this out it runs fine -- is
there
> > any way to optimize it ? I had a similar problem with just Category so
I
> > created a new field in the product file called FullCat which combined
> > SuperCategory and Category and thus eliminating the 2nd AND clause --
and
> > that fixed it -- I just didn't want to do the same thing with Publisher.
> > Before I tried to index Category, SuperCategory ... nothing seemed to
help
>
> Have you run a VACUUM ANALYZE on the table? And what does
> EXPLAIN show for the query?
>
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2001-01-29 16:36:44 | Re: BLOB HOWTO?? |
Previous Message | robert gravsjo | 2001-01-29 16:19:21 | Re: BLOB HOWTO?? |