From: Kevin Grittner <kgrittn@ymail.com>
To: Jeff Janes <jeff.janes@gmail.com>
To: Bartłomiej Romański <br@sentia.pl>
Cc: pgsql-performance@postgresql.org <pgsql-performance@postgresql.org>
Subject: Re: Planner performance extremely affected by an hanging transaction (20-30 times)?
Date: Mon, 23 Sep 2013 07:00:16 -0700 (PDT)
Message-ID: <1379944816.30390.YahooMailNeo@web162903.mail.bf1.yahoo.com> (raw)
In-Reply-To: <CAMkU=1wjnoFOrzVqLpUg2Ja=+kd_sv2HP4+cF-Y7r4a3uHT-tg@mail.gmail.com>
References: <CAC6=Lj7fYUWzcKLU6X7-8D1q+ijvBrGmwS2dw4mixhH8F8KSAw@mail.gmail.com>
<CAMkU=1wjnoFOrzVqLpUg2Ja=+kd_sv2HP4+cF-Y7r4a3uHT-tg@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-performance>
Jeff Janes <jeff.janes@gmail.com> wrote:
> 1) The planner actually queries the relation to find the end
> points of the variable ranges, rather than using potentially
> out-of-date statistics.
Are we talking about the probe for the end (or beginning) of an
index? If so, should we even care about visibility of the row
related to the most extreme index entry? Should we even go to the
heap during the plan phase?
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance
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: kgrittn@ymail.com, jeff.janes@gmail.com, br@sentia.pl
Subject: Re: Planner performance extremely affected by an hanging transaction (20-30 times)?
In-Reply-To: <1379944816.30390.YahooMailNeo@web162903.mail.bf1.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