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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Kevin Grittner <kgrittn(at)ymail(dot)com>
Cc: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Bartłomiej Romański <br(at)sentia(dot)pl>, "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-24 10:35:47
Message-ID: 5815.1380018947@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Kevin Grittner <kgrittn(at)ymail(dot)com> writes:
> 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?

Consider the case where some transaction inserted a wildly out-of-range
value, then rolled back. If we don't check validity of the heap row,
we'd be using that silly endpoint value for planning purposes ---
indefinitely. That's not an improvement over the situation that the
probe is meant to fix.

regards, tom lane

In response to

Responses

Browse pgsql-performance by date

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