pg.ddx.io pgsql-admin@postgresql.org mailing list archivehelp / color / mirror / Atom feed
From: Abu Mushayeed <abumushayeed@yahoo.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-admin@postgresql.org
Subject: Re: Plannner favoring nested loop
Date: Mon, 7 May 2007 15:30:01 -0700 (PDT)
Message-ID: <952451.30909.qm@web57105.mail.re3.yahoo.com> (raw)
In-Reply-To: <19019.1178573853@sss.pgh.pa.us>
My default_statistics_target in the postgresql.conf file is set at 250. The tables are vacuumed everyday. Now, does that mean, for each column or only for the column on which index exist, increase the value of "statistics" value, so while analyzing it uses more rows in the sample.
Thanks
Abu
Tom Lane <tgl@sss.pgh.pa.us> wrote:
Abu Mushayeed writes:
> I am trying to determine if I can make the planner see that nested loop is very expensive while it is trying to do an plan for a query and not pick that route.
If it's doing that when it shouldn't, it's probably because it's
underestimated the number of rows in the outer relation. Look to your
stats settings.
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend
---------------------------------
Ahhh...imagining that irresistible "new car" smell?
Check outnew cars at Yahoo! Autos.
view thread (3+ messages)
Message-ID: <952451.30909.qm@web57105.mail.re3.yahoo.com> Permalink: ../952451.30909.qm@web57105.mail.re3.yahoo.com/ Also on: postgresql.org/message-id/952451.30909.qm@web57105.mail.re3.yahoo.com ·
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-admin@postgresql.org Cc: abumushayeed@yahoo.com, tgl@sss.pgh.pa.us Subject: Re: Plannner favoring nested loop In-Reply-To: <952451.30909.qm@web57105.mail.re3.yahoo.com> * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions for how to clone and mirror all data and code used for this inbox