From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Greg Stark <gsstark(at)mit(dot)edu>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: branching for 9.2devel |
Date: | 2011-04-25 20:55:33 |
Message-ID: | 4DB5DFC5.4010001@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 04/25/2011 04:28 PM, Tom Lane wrote:
> Andrew Dunstan<andrew(at)dunslane(dot)net> writes:
>> On 04/25/2011 03:30 PM, Tom Lane wrote:
>>> *Ouch*. Really? It's hard to believe that anyone would consider it
>>> remotely usable for more than toy-sized projects, if you have to list
>>> all the typedef names on the command line.
>> Looks like BSD does the same. It's just that we hide it in pgindent:
> Oh wow, I never noticed that. That's going to be a severe problem for
> the "run it anywhere" goal. The typedefs list is already close to 32K,
> and is not going anywhere but up. There are already platforms on which
> a shell command line that long will fail, and I think once we break past
> 32K we might find it failing on even pretty popular ones.
>
>
Well, my solution would be to replace pgindent with a perl script (among
other advantages, it would then run everywhere we build, including
Windows), and filter the typedefs list so that we only use the ones
that appear in each file with that file, instead of passing the whole
list to each file.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Merlin Moncure | 2011-04-25 20:57:50 | Re: "stored procedures" - use cases? |
Previous Message | Yves Weißig | 2011-04-25 20:47:18 | Re: operator classes for index? |