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

From: Jesper Krogh <jesper(at)krogh(dot)cc>
To: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
Cc: 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-21 05:08:20
Message-ID: 51CA92A1-7109-4539-8990-0A111E48E943@krogh.cc
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance


On 21/09/2013, at 00.01, Jeff Janes <jeff(dot)janes(at)gmail(dot)com> wrote:
> See "In progress INSERT wrecks plans on table" and "Performance bug in prepared statement binding in 9.2" also on this list

This feels like the same
http://postgresql.1045698.n5.nabble.com/Slow-query-plan-generation-fast-query-PG-9-2-td5769363.html

>
> The issues are:
>
> 1) The planner actually queries the relation to find the end points of the variable ranges, rather than using potentially out-of-date statistics.
>

In my app i would prefer potentially out-of-date statistics instead.

Jesper

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Kevin Grittner 2013-09-23 14:00:16 Re: Planner performance extremely affected by an hanging transaction (20-30 times)?
Previous Message Jeff Janes 2013-09-20 22:01:33 Re: Planner performance extremely affected by an hanging transaction (20-30 times)?