Message-ID: <4A33AAC7.2000008@dunslane.net>
Date: Sat, 13 Jun 2009 09:33:59 -0400
From: Andrew Dunstan <andrew@dunslane.net>
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US;
	rv:1.8.0.12) Gecko/20071019 Fedora/1.0.9-3.fc6 pango-text
	SeaMonkey/1.0.9
MIME-Version: 1.0
To: Peter Eisentraut <peter_e@gmx.net>
CC: pgsql-hackers@postgresql.org, Tom Lane <tgl@sss.pgh.pa.us>,
	Bruce Momjian <bruce@momjian.us>
Subject: Re: pgindent run coming
References: <200906101950.n5AJoFP01545@momjian.us>
	<200906102344.53483.peter_e@gmx.net>
	<13137.1244667281@sss.pgh.pa.us>
	<200906131613.53870.peter_e@gmx.net>
In-Reply-To: <200906131613.53870.peter_e@gmx.net>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
Content-Transfer-Encoding: 7bit


Peter Eisentraut wrote:
> On Wednesday 10 June 2009 23:54:41 Tom Lane wrote:
>   
>> Peter Eisentraut <peter_e@gmx.net> writes:
>>     
>>>>> I think it usually does that already ...
>>>>>           
>>> Um, attached you will find a bunch of counterexamples.
>>>       
>> At a quick look, I'm not sure that any of these are in code that hasn't
>> been edited since the 8.3 pgindent run.
>>     
>
> So what does that mean then?  Surely pgindent doesn't keep track of what has 
> been edited when?
>
>   

If the code has been edited since the last pgindent run, then pgindent 
hasn't had a chance to adjust it, no?

cheers

andrew