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

Re: Further pg_upgrade analysis for many tables

From: Jeff Janes <jeff(dot)janes(at)gmail(dot)com>
To: Simon Riggs <simon(at)2ndquadrant(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 17:50:38
Message-ID: CAMkU=1wDGLemnJ_DyrQGiq42zvpbukCJ6eN0z+YjVegOXRbi+g@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-hackers
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.

Cheers,

Jeff


In response to

Responses

pgsql-hackers by date

Next:From: Tom LaneDate: 2013-01-09 17:50:52
Subject: Re: PL/perl should fail on configure, not make
Previous:From: Tom LaneDate: 2013-01-09 17:32:20
Subject: Re: [PATCH] unified frontend support for pg_malloc et al and palloc/pfree mulation (was xlogreader-v4)

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