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

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: pgsql-performance(at)postgresql(dot)org
Subject: Re: Planner performance extremely affected by an hanging transaction (20-30 times)?
Date: 2013-09-25 17:36:24
Message-ID: 52431F18.9070102@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On 09/25/2013 12:06 AM, Jeff Janes wrote:
>> Why do we need a procarraylock for this? Seems like the solution would
>> be not to take a lock at all; the information on transaction commit is
>> in the clog, after all.
>>
>
> My understanding is that you are not allowed to check the clog until after
> you verify the transaction is no longer in progress, otherwise you open up
> race conditions.

In this particular case, I'd argue that we don't care about race
conditions -- it's a plan estimate. We certainly care about them a lot
less than lock-blocks.

--
Josh Berkus
PostgreSQL Experts Inc.
http://pgexperts.com

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Andres Freund 2013-09-25 17:53:13 Re: Planner performance extremely affected by an hanging transaction (20-30 times)?
Previous Message Josh Berkus 2013-09-25 17:29:15 Re: Why is n_distinct always -1 for range types?