Re: pgsql: Refactor NUM_cache_remove calls in error report path to a PG_TRY

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: pgsql: Refactor NUM_cache_remove calls in error report path to a PG_TRY
Дата
Msg-id 26144.1249944724@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: pgsql: Refactor NUM_cache_remove calls in error report path to a PG_TRY  (Robert Haas <robertmhaas@gmail.com>)
Ответы Re: pgsql: Refactor NUM_cache_remove calls in error report path to a PG_TRY  (Robert Haas <robertmhaas@gmail.com>)
Список pgsql-committers
Robert Haas <robertmhaas@gmail.com> writes:
> On Mon, Aug 10, 2009 at 4:31 PM, Tom Lane<tgl@sss.pgh.pa.us> wrote:
>> Yeah --- if there are any active patches against that code (a fact not
>> in evidence) then reindenting now would break them now. �Leaving it till
>> the next pgindent run seems fine to me.

> But if there are patches against that code, then they've been broken
> now

Uh, no --- the point here is that something like two hundred lines of
code were *not* changed by reindenting.  Diffs in that area would likely
still apply.

> and they will break again when the pgindent run is done.

Only if they aren't applied by then.  One reason that we normally only
run pgindent at the end of the devel cycle is that that's when
(presumably) the smallest amount of patches remain outstanding.

            regards, tom lane

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

Предыдущее
От: alvherre@postgresql.org (Alvaro Herrera)
Дата:
Сообщение: pgsql: Fix URL to "The Hitch-Hiker's Guide to Evolutionary Computation".
Следующее
От: Robert Haas
Дата:
Сообщение: Re: pgsql: Refactor NUM_cache_remove calls in error report path to a PG_TRY