DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=ymail.com;
 h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding;
 b=Wg8qOaPEtm48P6LsrkNV6O9w9UT6mjzUXjDBQ+vv9szOp+PAechdsHNXBW3Lx04ol03lxOZ9DF/aitIKyZfgkaxHU+5UUlH4AVf1xIpWZUyZToXmXjdCInJBJLyYvnK3WC/I7A5jmCBR6asoCsq1xs8tl1xf6KRpLZF+SMaP24s=;
References: 
 <CAC6=Lj7fYUWzcKLU6X7-8D1q+ijvBrGmwS2dw4mixhH8F8KSAw@mail.gmail.com>
 <CAMkU=1wjnoFOrzVqLpUg2Ja=+kd_sv2HP4+cF-Y7r4a3uHT-tg@mail.gmail.com>
Message-ID: <1379944816.30390.YahooMailNeo@web162903.mail.bf1.yahoo.com>
Date: Mon, 23 Sep 2013 07:00:16 -0700 (PDT)
From: Kevin Grittner <kgrittn@ymail.com>
Reply-To: Kevin Grittner <kgrittn@ymail.com>
Subject: Re: Planner performance extremely affected by an hanging transaction
 (20-30 times)?
To: Jeff Janes <jeff.janes@gmail.com>,
 =?utf-8?B?QmFydMWCb21pZWogUm9tYcWEc2tp?= <br@sentia.pl>
Cc: "pgsql-performance@postgresql.org" <pgsql-performance@postgresql.org>
In-Reply-To: 
 <CAMkU=1wjnoFOrzVqLpUg2Ja=+kd_sv2HP4+cF-Y7r4a3uHT-tg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Precedence: bulk
Sender: pgsql-performance-owner@postgresql.org

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?=C2=A0 If so, should we even care about visibility of the row
related to the most extreme index entry?=C2=A0 Should we even go to the
heap during the plan phase?

--=20
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


--=20
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance