| From: | "Marko Kreen" <markokr(at)gmail(dot)com> |
|---|---|
| To: | "Kai Hessing" <kai(dot)hessing(at)hobsons(dot)de> |
| Cc: | "pgsql general" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Performance Killer 'IN' ? |
| Date: | 2006-04-03 14:14:45 |
| Message-ID: | e51f66da0604030714q103b709dmb8454a9897c30580@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 4/3/06, Kai Hessing <kai(dot)hessing(at)hobsons(dot)de> wrote:
> Marko Kreen wrote:
> > Just a shot in the dark: does the plan stay the same,
> > when you remove the ' AND status > -1' ?
>
> No difference: I skipped the 'AND status > -1' and have the following
> results...
Ok. Thanks. I once had similar query and it seemed that postgres
got confused if there was big IN and alse something else in WHERE
clause. Dropping the rest got postgres to use index for IN.
But I did not have time to research it then and with your result
seems it's not a problem in recent versions.
--
marko
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-04-03 14:15:48 | Re: Performance Killer 'IN' ? |
| Previous Message | chris smith | 2006-04-03 13:58:36 | Re: what is this error |