Re: Disabling nested loops - worst case performance

From: Claudio Freire <klaussfreire(at)gmail(dot)com>
To: pgsql-performance(at)postgresql(dot)org
Subject: Re: Disabling nested loops - worst case performance
Date: 2011-03-18 15:26:20
Message-ID: AANLkTikdXec-hR4hAo5kVyQyrdt-qKRqhYYCmLBxT-A1@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Fri, Mar 18, 2011 at 7:52 AM, Vitalii Tymchyshyn <tivv00(at)gmail(dot)com> wrote:
> 18.03.11 09:15, Anssi Kääriäinen написав(ла):
> Hello.
>
> If your queries work on single attribute, you can try adding partial indexes
> for different attributes. Note that in this case parameterized statements
> may prevent index usage, so check also with attribute id inlined.

And if your queries work on a single entity instead, you can partition
the table per-entity thus "teach" the database enging about the
correlation.

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message tv 2011-03-18 15:30:19 Re: Help with Query Tuning
Previous Message Kevin Grittner 2011-03-18 14:38:05 Re: Fastest pq_restore?