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

Поиск
Список
Период
Сортировка
От Simon Riggs
Тема Re: reducing the overhead of frequent table locks - now, with WIP patch
Дата
Msg-id BANLkTinBGrQwW0s_BQ32vA1z=457LMfBDw@mail.gmail.com
обсуждение исходный текст
Ответ на Re: reducing the overhead of frequent table locks - now, with WIP patch  (Robert Haas <robertmhaas@gmail.com>)
Ответы Re: reducing the overhead of frequent table locks - now, with WIP patch  (Stephen Frost <sfrost@snowman.net>)
Re: reducing the overhead of frequent table locks - now, with WIP patch  ("Kevin Grittner" <Kevin.Grittner@wicourts.gov>)
Re: reducing the overhead of frequent table locks - now, with WIP patch  (Robert Haas <robertmhaas@gmail.com>)
Re: reducing the overhead of frequent table locks - now, with WIP patch  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
On Tue, Jun 7, 2011 at 6:33 PM, Robert Haas <robertmhaas@gmail.com> wrote:
> On Tue, Jun 7, 2011 at 1:27 PM, Joshua Berkus <josh@agliodbs.com> wrote:
>> As long as we have solidarity of the committers that this is not allowed, however, this is not a real problem.  And
itappears 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


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Heikki Linnakangas
Дата:
Сообщение: Re: SIREAD lock versus ACCESS EXCLUSIVE lock
Следующее
От: Tom Lane
Дата:
Сообщение: Re: SIREAD lock versus ACCESS EXCLUSIVE lock