pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Josh Berkus <josh@agliodbs.com>
To: pgsql-performance@postgresql.org
Subject: Re: Planner performance extremely affected by an hanging transaction (20-30 times)?
Date: Wed, 25 Sep 2013 10:36:24 -0700
Message-ID: <52431F18.9070102@agliodbs.com> (raw)
In-Reply-To: <WM!38da9b102bb079ff6de748b7d29d9331c1562967d0c90bcb85fb5b8b0c62a2a15900f90acff261ba7877ef83f656f6c0!@asav-1.01.com>
References: <CAC6=Lj7fYUWzcKLU6X7-8D1q+ijvBrGmwS2dw4mixhH8F8KSAw@mail.gmail.com>
	<CAMkU=1wjnoFOrzVqLpUg2Ja=+kd_sv2HP4+cF-Y7r4a3uHT-tg@mail.gmail.com>
	<1379944816.30390.YahooMailNeo@web162903.mail.bf1.yahoo.com>
	<5815.1380018947@sss.pgh.pa.us>
	<e8795f5e292a0bd1a4d8ebbcb54e4a98.squirrel@shrek.krogh.cc>
	<WM!41fcd3fa079d542735fe69d3254859689c1085f7c897fa6e9a9b828ad9d2c80ba7b6b2c4c67c942a6115262993147370!@asav-1.01.com>
	<5241CF2A.2070309@agliodbs.com>
	<CAMkU=1ys-fB2Nczt=LT1pVHzK3Jv4Jb-67N29Gzyx3nraweoZQ@mail.gmail.com>
	<WM!38da9b102bb079ff6de748b7d29d9331c1562967d0c90bcb85fb5b8b0c62a2a15900f90acff261ba7877ef83f656f6c0!@asav-1.01.com>
List-Unsubscribe:  <mailto:majordomo@postgresql.org?body=unsub%20pgsql-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


-- 
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance



view thread (25+ messages)  latest in thread

Message-ID: <52431F18.9070102@agliodbs.com>
Permalink:  ../52431F18.9070102@agliodbs.com/
Also on:    postgresql.org/message-id/52431F18.9070102@agliodbs.com

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: josh@agliodbs.com
  Subject: Re: Planner performance extremely affected by an hanging transaction (20-30 times)?
  In-Reply-To: <52431F18.9070102@agliodbs.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox