From: | Heikki Linnakangas <heikki(at)enterprisedb(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Chris Browne <cbbrowne(at)acm(dot)org>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Lessons from commit fest |
Date: | 2008-04-17 06:11:12 |
Message-ID: | 4806EA00.9020701@enterprisedb.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Alvaro Herrera wrote:
> Bruce Momjian wrote:
>> Alvaro Herrera wrote:
>
>>> Maybe this means that we should give pgindent a run over the back
>>> branches.
>> Yea, that thought has crossed our minds, but the problem is that there
>> is little testing of back branches so it would be risky.
>
> That's a fair point, though I wonder how can a code indenter be so
> broken that it broke code in ways not detected by our buildfarm.
Something like this:
if (foo)
{
do something;
do something else;
}
...
->
if (foo)
do something;
do something else;
...
I wouldn't be too surprised if something like that happened with one of
the complex macros, like PG_TRY/CATCH.
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2008-04-17 06:20:50 | Re: Patch for Prevent pg_dump/pg_restore from being affected by statement_timeout |
Previous Message | Bryce Nesbitt | 2008-04-17 04:12:47 | Re: Proposed patch - psql wraps at window width |