Re: Can we avoid chdir'ing in resolve_symlinks() ?
От | Tom Lane |
---|---|
Тема | Re: Can we avoid chdir'ing in resolve_symlinks() ? |
Дата | |
Msg-id | 1776365.1663013239@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: Can we avoid chdir'ing in resolve_symlinks() ? (Peter Eisentraut <peter.eisentraut@enterprisedb.com>) |
Ответы |
Re: Can we avoid chdir'ing in resolve_symlinks() ?
|
Список | pgsql-hackers |
Peter Eisentraut <peter.eisentraut@enterprisedb.com> writes: > On 12.09.22 17:33, Tom Lane wrote: >> Are you proposing we give up the support for relocatable installations? >> I'm not here to defend that feature, but I bet somebody will. (And >> doesn't "make check" depend on it?) > I'm complaining specifically about the resolving of symlinks. Why does > $ /usr/local/opt/postgresql@13/bin/pg_config --bindir > print > /usr/local/Cellar/postgresql@13/13.8/bin > when it clearly should print > /usr/local/opt/postgresql@13/bin I'm not sure about your setup there, but if you mean that /usr/local/opt/postgresql@13/bin is a symlink reading more or less "./13.8/bin", I doubt that failing to canonicalize that is a good idea. The point of finding the bindir is mainly to be able to navigate to its sibling directories such as lib/, etc/, share/. There's no certainty that a symlink leading to the bin directory will have sibling symlinks to those other directories. regards, tom lane
В списке pgsql-hackers по дате отправления: