| From: | Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Dagfinn Ilmari Mannsåker <ilmari(at)ilmari(dot)org>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: multi-install PostgresNode |
| Date: | 2021-03-25 08:23:22 |
| Message-ID: | 21f666f8-3e73-db55-e650-b837bf31c5b1@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 25.03.21 04:47, Michael Paquier wrote:
> On Wed, Mar 24, 2021 at 03:33:51PM -0300, Alvaro Herrera wrote:
>> On 2021-Mar-24, Andrew Dunstan wrote:
>>> +# The install path set in get_new_node needs to be a directory containing
>>> +# bin and lib subdirectories as in a standard PostgreSQL installation, so this
>>> +# can't be used with installations where the bin and lib directories don't have
>>> +# a common parent directory.
>>
>> I've never heard of an installation where that wasn't true. If there
>> was a need for that, seems like it'd be possible to set them with
>> { bindir => ..., libdir => ...} but I doubt it'll ever be necessary.
>
> This would imply an installation with some fancy --bindir or --libdir
> specified in ./configure. Never say never, but I also think that what
> has been committed is fine.
/usr/lib64/? /usr/lib/x86_64-linux-gnu/? Seems pretty common.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Markus Wanner | 2021-03-25 08:36:58 | Re: [PATCH] Provide more information to filter_prepare |
| Previous Message | Pavel Stehule | 2021-03-25 08:05:43 | Re: proposal: schema variables - doc |