From: | Thomas Hallgren <thhal(at)mailblocks(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Dave Page <dpage(at)vale-housing(dot)co(dot)uk>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: pgxs and pginstaller |
Date: | 2005-09-23 14:21:08 |
Message-ID: | thhal-02acPBHdl8bQknqzIQeLDLW8B89tQ0h@mailblocks.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
>"Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> writes:
>
>
>>>My temporary patch for this was to remove all lines staring
>>>with 'ifeq'
>>>or 'endif' between line 66 and 102.
>>>
>>>
>
>
>
>>I agree with your earlier comment - this should definitely be fixed in
>>PostgreSQL, not pgInstaller.
>>
>>
>
>It's not broken, and I've seen no argument as to why we ought to change it.
>
>
Well, at least make it case insensitive so that a location containing
PostgreSQL doesn't cause this behavior.
But quite frankly, wouldn't it be much better if the rule(s) was based
on known "common locations" rather than to just assume that it is a such
if it doesn't contain the string postgres? You are limiting the valid
settings of the 'prefix' option quite a bit at present. Why?
Regards,
Thomas Hallgren
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-09-23 14:21:28 | Re: stack depth limit exceeded problem. |
Previous Message | Tom Lane | 2005-09-23 14:16:01 | Re: pgxs and pginstaller |