Re: Wrong plan for simple join with index on FK - Mailing list pgsql-hackers

From Zeugswetter Andreas DCP SD
Subject Re: Wrong plan for simple join with index on FK
Date
Msg-id E1539E0ED7043848906A8FF995BDA579010543B4@m0143.s-mxs.net
Whole thread Raw
In response to Wrong plan for simple join with index on FK  ("Pavel Stehule" <pavel.stehule@hotmail.com>)
Responses Re: Wrong plan for simple join with index on FK
List pgsql-hackers
> >These are all minor abberations though, on the whole the estimates
are
> >pretty good. Perhaps you need to tweak the values of random_page_cost
> >and similar variables.
>
> Thank You, It's general problem or only mine? I have "100%"
> standard current PC.

The default random_page_cost assumes some concurrent activity. If your
PC does nothing else concurrently, the performance of a seq scan will
be underestimated.

Try to do the statement with some concurrent disk load and you will most
likely
see that the 1. plan is faster. (assuming the tables are not fully
cached)

Andreas


pgsql-hackers by date:

Previous
From: "Pavel Stehule"
Date:
Subject: Re: Wrong plan for simple join with index on FK
Next
From: "Pavel Stehule"
Date:
Subject: Re: Wrong plan for simple join with index on FK