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

Поиск
Список
Период
Сортировка
Искать
От
Alvaro Herrera
Тема
Re: pgsql: Refactor NUM_cache_remove calls in error report path to a PG_TRY
Дата
Msg-id
20090810202247.GG4796@alvh.no-ip.org
Ответ на
Список
Дерево обсуждения
pgsql: Refactor NUM_cache_remove calls in error report path to a PG_TRY alvherre@postgresql.org (Alvaro Herrera)
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 Alvaro Herrera <alvherre@commandprompt.com>
Re: pgsql: Refactor NUM_cache_remove calls in error report path to a PG_TRY Tom Lane <tgl@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 Tom Lane <tgl@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>
Robert Haas escribió:
> On Mon, Aug 10, 2009 at 4:16 PM, Alvaro Herrera wrote:
> > Log Message:
> > -----------
> > Refactor NUM_cache_remove calls in error report path to a PG_TRY block.
> >
> > The code in the new block was not reindented; it will be fixed by pgindent
> > eventually.
> 
> ...breaking every patch that someone has in progress against that code?

I guess I neglected to add "a year from now or so".  I'm not in a hurry
to run pgindent.

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
В списке pgsql-committers по дате отправления
От: Robert Haas
Дата:
От: Robert Haas
Дата:
FAQ