Horton

Re: foreign key locks, 2nd attempt

Alvaro Herrera <alvherre@commandprompt.com>

View thread
From: Alvaro Herrera <alvherre@commandprompt.com>
To: Bruce Momjian <bruce@momjian.us>
Cc: Robert Haas <robertmhaas@gmail.com>, Simon Riggs <simon@2ndquadrant.com>, Tom Lane <tgl@sss.pgh.pa.us>, Noah Misch <noah@leadboat.com>, Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2012-03-16T18:49:03Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Try to avoid running with a full fsync request queue.

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@momjian.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@2ndquadrant.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@commandprompt.com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support