Re: foreign key locks, 2nd attempt

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Simon Riggs <simon(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Noah Misch <noah(at)leadboat(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: foreign key locks, 2nd attempt
Date: 2012-03-16 18:49:03
Message-ID: 1331923720-sup-3214@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


Excerpts from Bruce Momjian's message of vie mar 16 15:22:05 -0300 2012:
>
> On Fri, Mar 16, 2012 at 10:08:07AM -0400, Robert Haas wrote:
> > On Thu, Mar 15, 2012 at 11:09 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> > > On Tue, Mar 13, 2012 at 01:46:24PM -0400, Robert Haas wrote:
> > >> On Mon, Mar 12, 2012 at 3:28 PM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> > >> > I agree with you that some worst case performance tests should be
> > >> > done. Could you please say what you think the worst cases would be, so
> > >> > those can be tested? That would avoid wasting time or getting anything
> > >> > backwards.
> > >>
> > >> I've thought about this some and here's what I've come up with so far:
> > >
> > > I question whether we are in a position to do the testing necessary to
> > > commit this for 9.2.
> >
> > Is anyone even working on testing it?
>
> No one I know of. I am just trying to set expectations that this still
> has a long way to go.

A Command Prompt colleague is on it.

--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Stuart Bishop 2012-03-16 18:57:29 Re: [BUGS] BUG #6532: pg_upgrade fails on Python stored procedures
Previous Message Simon Riggs 2012-03-16 18:25:56 Incorrect assumptions with low LIMITs