Re: pgsql: Refactor NUM_cache_remove calls in error report path to a PG_TRY - Mailing list pgsql-committers

From Tom Lane
Subject Re: pgsql: Refactor NUM_cache_remove calls in error report path to a PG_TRY
Date
Msg-id 24084.1249936315@sss.pgh.pa.us
Whole thread Raw
In response to Re: pgsql: Refactor NUM_cache_remove calls in error report path to a PG_TRY  (Alvaro Herrera <alvherre@commandprompt.com>)
Responses Re: pgsql: Refactor NUM_cache_remove calls in error report path to a PG_TRY
List pgsql-committers
Alvaro Herrera <alvherre@commandprompt.com> writes:
> Robert Haas escribi�:
>>> 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.

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.

            regards, tom lane

pgsql-committers by date:

Previous
From: Robert Haas
Date:
Subject: Re: pgsql: Refactor NUM_cache_remove calls in error report path to a PG_TRY
Next
From: Robert Haas
Date:
Subject: Re: pgsql: Refactor NUM_cache_remove calls in error report path to a PG_TRY