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

help / color / mirror / Atom feed
From: Josh Berkus <josh@agliodbs.com>
To: Abhijit Menon-Sen <ams@2ndQuadrant.com>
Cc: Simon Riggs <simon@2ndQuadrant.com>
Cc: Mark Kirkwood <mark.kirkwood@catalyst.net.nz>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Gavin Flower <gavinflower@archidevsys.co.nz>
Cc: pgsql-hackers@postgresql.org
Subject: Re: [PERFORM] In progress INSERT wrecks plans on table
Date: Wed, 10 Jul 2013 09:47:34 -0700
Message-ID: <51DD9026.2030107@agliodbs.com> (raw)
In-Reply-To: <WM!26a3c5a0f97d399bf3d258d64ee1eee5843f0b45f9801c411e8f5e0770f3c25a892f527c93229c57bfa8f0f3eb6066dc!@asav-2.01.com>
References: <5179F5C6.8070702@archidevsys.co.nz>
	<5180E3C8.3010201@catalyst.net.nz>
	<2121.1367417215@sss.pgh.pa.us>
	<5181B80D.70404@catalyst.net.nz>
	<CA+U5nMKYYZDekhtxz1E1B11dAm9UJoHBQHrB6DiiZDJo3fLd0Q@mail.gmail.com>
	<916bff05a5ab130c76d7835abbaf7762.squirrel@mail.catalyst.net.nz>
	<CA+U5nMJHjQccVSB3SkAHdRn2AfuuO49wA8-ZGB366cddTynjdQ@mail.gmail.com>
	<CA+U5nMKMfZUEimZ9=oF2wJ-WkiGhMw3mQjUFT6PBGofUpmXL8A@mail.gmail.com>
	<51870CB6.6090404@catalyst.net.nz>
	<CA+U5nMJHgHczmWrKzst=PJeP+9BHJAsTgRNXyVZX5Oyys2zn_g@mail.gmail.com>
	<20130624044350.GA32322@toroid.org>
	<WM!ecf8a06e8ffb427fca7f6e0f4ff5638515a78282eced37d2e4f9981c1e769de67caec13f84aa60888557e9af7b43dca1!@asav-2.01.com>
	<51DAF2C8.6010705@agliodbs.com>
	<WM!26a3c5a0f97d399bf3d258d64ee1eee5843f0b45f9801c411e8f5e0770f3c25a892f527c93229c57bfa8f0f3eb6066dc!@asav-2.01.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>

On 07/08/2013 10:11 AM, Josh Berkus wrote:
> On 06/23/2013 09:43 PM, Abhijit Menon-Sen wrote:
>> (Cc: to pgsql-performance dropped, pgsql-hackers added.)
>>
>> At 2013-05-06 09:14:01 +0100, simon@2ndQuadrant.com wrote:
>>>
>>> New version of patch attached which fixes a few bugs.
>>
>> I read the patch, but only skimmed the earlier discussion about it. In
>> isolation, I can say that the patch applies cleanly and looks sensible
>> for what it does (i.e., cache pgprocno to speed up repeated calls to
>> TransactionIdIsInProgress(somexid)).
>>
>> In that sense, it's ready for committer, but I don't know if there's a
>> better/more complete/etc. way to address the original problem.
> 
> Has this patch had performance testing?  Because of the list crossover I
> don't have any information on that.

Due to the apparent lack of performance testing, I'm setting this back
to "needs review".

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


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



view thread (42+ messages)  latest in thread

Message-ID: <51DD9026.2030107@agliodbs.com>
Permalink:  ../51DD9026.2030107@agliodbs.com/
Also on:    postgresql.org/message-id/51DD9026.2030107@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, ams@2ndQuadrant.com, simon@2ndQuadrant.com, mark.kirkwood@catalyst.net.nz, tgl@sss.pgh.pa.us, gavinflower@archidevsys.co.nz, pgsql-hackers@postgresql.org
  Subject: Re: [PERFORM] In progress INSERT wrecks plans on table
  In-Reply-To: <51DD9026.2030107@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