Re: Performance issues

From: Josh Krupka <jkrupka(at)gmail(dot)com>
To: vjoshi(at)zetainteractive(dot)com
Cc: PostgreSQL Performance <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Performance issues
Date: 2015-03-21 07:39:48
Message-ID: CAB6McgX5_8AxJzBYo2Sp=NfRHg7tWe5x7MrxibBGbs1LfAV=4Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

The other approaches of fixing the estimates, cost params, etc are the
right way of fixing it. *However* if you needed a quick fix for just this
report and can't find a way of setting it in Jaspersoft for just the report
(I don't think it will let you run multiple sql statements by default,
maybe not at all) there are still a couple more options. You can define a
new datasource in jasper, point this report to that datasource, and have
that new datasource configured to not use the nested loops. You could do
that either by making the new datasource use a different user than
everything else, and disable nested loops for that user in postgres, or you
could probably have the datasource initialization process disable nested
loops.

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Maxim Boguk 2015-03-21 09:10:59 Re: Query RE: Optimising UUID Lookups
Previous Message Roland Dunn 2015-03-20 19:01:20 Query RE: Optimising UUID Lookups