Re: IN vs EXISTS - Mailing list pgsql-general

From askel
Subject Re: IN vs EXISTS
Date
Msg-id 93a79e8c-e923-4a80-b373-bca674a3a464@z72g2000hsb.googlegroups.com
Whole thread Raw
In response to IN vs EXISTS  (askel <dummy666@mail.ru>)
List pgsql-general
Tom,

I'm using 8.3.1. I did run EXPLAIN but have never familiarized myself
with how to read/use it beside simple comparing cost estimation and
whether there is any seq scan that can benefit from creating index.

Thanks for replying

On Jun 7, 11:19 am, t...@sss.pgh.pa.us (Tom Lane) wrote:
> askel <dummy...@mail.ru> writes:
> > Performance is at least few times better when EXISTS is used.
>
> It really shouldn't be.  PG knows more possible plans for IN than
> EXISTS, so IN should pretty much always be equal or better ... unless
> the planner is making the wrong choice.  I speculate that you have
> out-of-date statistics or some such.  Have you compared EXPLAIN ANALYZE
> output for the two cases?  Which PG version are we talking about?
>
>                         regards, tom lane
>
> --
> Sent via pgsql-general mailing list (pgsql-gene...@postgresql.org)
> To make changes to your subscription:http://www.postgresql.org/mailpref/pgsql-general


pgsql-general by date:

Previous
From: "Bojan"
Date:
Subject: pl/pgsql function with argument of type DATE
Next
From: Giorgio Valoti
Date:
Subject: to_tsvector: error with italian configuration