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

From: Kevin Grittner <kgrittn(at)ymail(dot)com>
To: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Bartłomiej Romański <br(at)sentia(dot)pl>
Cc: "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Planner performance extremely affected by an hanging transaction (20-30 times)?
Date: 2013-09-23 14:00:16
Message-ID: 1379944816.30390.YahooMailNeo@web162903.mail.bf1.yahoo.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Jeff Janes <jeff(dot)janes(at)gmail(dot)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

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Sam Wong 2013-09-24 09:24:07 Slow plan for MAX/MIN or LIMIT 1?
Previous Message Jesper Krogh 2013-09-21 05:08:20 Re: Planner performance extremely affected by an hanging transaction (20-30 times)?