Re: Planner performance extremely affected by an hanging transaction (20-30 times)? - Mailing list pgsql-performance

From Kevin Grittner
Subject Re: Planner performance extremely affected by an hanging transaction (20-30 times)?
Date
Msg-id 1379944816.30390.YahooMailNeo@web162903.mail.bf1.yahoo.com
Whole thread Raw
In response to Re: Planner performance extremely affected by an hanging transaction (20-30 times)?  (Jeff Janes <jeff.janes@gmail.com>)
Responses Re: Planner performance extremely affected by an hanging transaction (20-30 times)?
List pgsql-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


pgsql-performance by date:

Previous
From: Jesper Krogh
Date:
Subject: Re: Planner performance extremely affected by an hanging transaction (20-30 times)?
Next
From: "Sam Wong"
Date:
Subject: Slow plan for MAX/MIN or LIMIT 1?