Re: sepgsql contrib module - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: sepgsql contrib module
Date
Msg-id AANLkTimDjFQzuEByt3dL_f5gberpifAneUh6CjAbNpFD@mail.gmail.com
Whole thread Raw
In response to Re: sepgsql contrib module  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: sepgsql contrib module  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Sun, Jan 23, 2011 at 03:19, Robert Haas <robertmhaas@gmail.com> wrote:
> 2011/1/21 KaiGai Kohei <kaigai@ak.jp.nec.com>:
>> Do we have any workaround to avoid these indenting/formatting?
>> Or, the reformatted code is better than before?
>
> That's pretty horrendous.  Tom/Bruce, any ideas?

I saw some similar things earlier, and it turned out to be two
different reasons in two different cases. In one case, it was because
I was using GNU indent, even though I thought I was using the one
that's on our ftp. But it does give a warning in that case, you just
have to actually *read* the warning. In the other case it was really
weird - when my wrapper script (that called pgindent with path
specification and such) executing using dash (the default /bin/sh on
Ubuntu), it did weird things - but when I explicitly executed the
wrapper script with /bin/bash, it worked - even though pgindent itself
is still using /bin/sh.

--
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: ALTER TYPE 2: skip already-provable no-work rewrites
Next
From: Michael Meskes
Date:
Subject: Re: Perl 5.12 complains about ecpg parser-hacking scripts