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 26144.1249944724@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  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: pgsql: Refactor NUM_cache_remove calls in error report path to a PG_TRY
List 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 by date:

Previous
From: alvherre@postgresql.org (Alvaro Herrera)
Date:
Subject: pgsql: Fix URL to "The Hitch-Hiker's Guide to Evolutionary Computation".
Next
From: Robert Haas
Date:
Subject: Re: pgsql: Refactor NUM_cache_remove calls in error report path to a PG_TRY