Search Postgresql Archives

Re: Problem with planner choosing nested loop

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Wed, Apr 2, 2008 at 1:06 PM, Harald Fuchs <hari.fuchs@xxxxxxxxxxxxxx> wrote:
> In article <a55915760804021107h4410dd93m33a6f94e28a83a2b@xxxxxxxxxxxxxx>,
>
> "Rodrigo E. De León Plicet" <rdeleonp@xxxxxxxxx> writes:
>
>  > On Wed, Apr 2, 2008 at 12:36 PM, Alex Solovey <a.solovey@xxxxxxxxx> wrote:
>  >> ... I have no idea how it could be fixed.
>
>  > - CREATE INDEX xifoo ON foo(bar_id);
>  > - ANALYZE;
>  > - Retry.
>
>  A compound index
>   CREATE INDEX xifoo2 ON foo (foo_a, bar_id)
>  might be more worthwhile.

And, if you're only interested in certain values of foo_a or bar_id
then partial indexes might be helpful but still cheap enough to
maintain in a large table.

-- 
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux