Re: Problem with planner choosing nested loop

From: "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com>
To: Rodrigo E(dot) De León Plicet <rdeleonp(at)gmail(dot)com>
Cc: "Alex Solovey" <a(dot)solovey(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: Problem with planner choosing nested loop
Date: 2008-04-02 18:27:34
Message-ID: dcc563d10804021127ie4c4e1br90f9c6722da4ae1b@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Apr 2, 2008 at 12:12 PM, Rodrigo E. De León Plicet
<rdeleonp(at)gmail(dot)com> wrote:
> Also important, consider creating additional indexes based on your
> access patterns.

Good point. Note that you can create indexes and then track their
usefulness with the pg_stat_user_indexes view, which I find incredibly
useful. In fact, all the pg_stat_ views are useful.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Peter Eisentraut 2008-04-02 18:28:00 Re: [GENERAL] SHA1 on postgres 8.3
Previous Message Alex Solovey 2008-04-02 18:20:47 Re: Problem with planner choosing nested loop