Skip site navigation (1) Skip section navigation (2)

Re: Further pg_upgrade analysis for many tables

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Magnus Hagander <magnus(at)hagander(dot)net>
Subject: Re: Further pg_upgrade analysis for many tables
Date: 2013-01-09 19:32:59
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On 9 January 2013 17:50, Jeff Janes <jeff(dot)janes(at)gmail(dot)com> wrote:
> On Wed, Jan 9, 2013 at 3:59 AM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
>> On 9 November 2012 18:50, Jeff Janes <jeff(dot)janes(at)gmail(dot)com> wrote:
>>> quadratic behavior in the resource owner/lock table
>> I didn't want to let that particular phrase go by without saying
>> "exactly what behaviour is that?", so we can discuss fixing that also.
> It is the thing that was fixed in commit eeb6f37d89fc60c6449ca1, "Add
> a small cache of locks owned by a resource owner in ResourceOwner."
> But that fix is only in 9.3devel.

That's good, it fixes the problem I reported in 2010, under
"SAVEPOINTs and COMMIT performance".

 Simon Riggs         
 PostgreSQL Development, 24x7 Support, Training & Services

In response to

pgsql-hackers by date

Next:From: Greg SmithDate: 2013-01-09 19:36:22
Subject: Re: buffer assertion tripping under repeat pgbench load
Previous:From: Karl O. PincDate: 2013-01-09 19:29:37
Subject: Re: [PATCH] PL/Python: Add spidata to all spiexceptions

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group