Re: reducing the overhead of frequent table locks - now, with WIP patch

From: Simon Riggs <simon(at)2ndQuadrant(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Joshua Berkus <josh(at)agliodbs(dot)com>, Alvaro Herrera <alvherre(at)commandprompt(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
Subject: Re: reducing the overhead of frequent table locks - now, with WIP patch
Date: 2011-06-07 18:06:32
Message-ID: BANLkTinBGrQwW0s_BQ32vA1z=457LMfBDw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jun 7, 2011 at 6:33 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Tue, Jun 7, 2011 at 1:27 PM, Joshua Berkus <josh(at)agliodbs(dot)com> wrote:
>> As long as we have solidarity of the committers that this is not allowed, however, this is not a real problem.  And it appears that we do.  In the future, it shouldn't even be necessary to discuss it.
>
> Solidarity?
>
> Simon - who was a committer last time I checked - seems to think that
> the current process is entirely bunko.

I'm not sure why anyone that disagrees with you should be accused of
wanting to junk the whole process. I've not said that and I don't
think this.

Before you arrived, it was quite normal to suggest tuning patches
after feature freeze.

--
 Simon Riggs                   http://www.2ndQuadrant.com/
 PostgreSQL Development, 24x7 Support, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2011-06-07 18:10:05 Re: SIREAD lock versus ACCESS EXCLUSIVE lock
Previous Message Robert Haas 2011-06-07 18:05:10 Re: BUG #6041: Unlogged table was created bad in slave node