public inbox for pgsql-performance@postgresql.org
help / color / mirror / Atom feedFrom: Gunther <raj@gusw.net>
To: pgsql-performance@postgresql.org
Subject: Re: query performance issue
Date: Wed, 15 Nov 2017 14:58:17 -0500
Message-ID: <31c10833-9d19-dfa5-1cab-43eaae097828@gusw.net> (raw)
In-Reply-To: <CAFj8pRC6xh=HDq1jwxW8n1Ct8=FbbdqHcx_VFHNCdNUz41rTWQ@mail.gmail.com>
References: <CAA=to3gXpr94TqSAYXT9zwxYwY_xKrLFnu8ZJNgJKP-kWza2CA@mail.gmail.com>
<CAFj8pRCyvCktcxtEQrmF4kw5oR1DNYd_4gJNd6mkjrHw_NPPPw@mail.gmail.com>
<CAA=to3gnNReZ62m3K3qbN_KL8Hnmrg4wfb4LefZYqUa9v4OOSQ@mail.gmail.com>
<CAFj8pRC6xh=HDq1jwxW8n1Ct8=FbbdqHcx_VFHNCdNUz41rTWQ@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
On 11/15/2017 8:12, Pavel Stehule wrote:
> There is wrong plan due wrong estimation
>
> for this query you should to penalize nested loop
>
> set enable_nestloop to off;
>
> before evaluation of this query
You are not the only one with this issue. May I suggest to look at this
thread a little earlier this month.
http://www.postgresql-archive.org/OLAP-reporting-queries-fall-into-nested-loops-over-seq-scans-or-ot...
where this has been discussed in some length.
regards,
-Gunther
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: raj@gusw.net
Subject: Re: query performance issue
In-Reply-To: <31c10833-9d19-dfa5-1cab-43eaae097828@gusw.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox