![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
LOG: could not open directory "/usr/share/timezone": No such file or directory What's it mean? Am I missing a package? |
#3
| |||
| |||
|
|
Hmmm ... where is that coming from exactly? PG itself should not be referring to /usr/share/timezone --- we have our own TZ database now. And glibc-based platforms don't keep their info there either (it's in /usr/share/zoneinfo, at least on my Fedora machine). So there's something awfully odd here. |
#4
| |||
| |||
|
|
Please. Also, what nondefault configuration or postgresql.conf settings are you using? |
#5
| |||
| |||
|
|
Please. Also, what nondefault configuration or postgresql.conf settings are you using? Sorry for delay. Attached. And --with-perl --with-odbc |
#6
| |||
| |||
|
|
As best I can tell, this is coming out because pgtz.c thinks that /usr/share/timezone is where Postgres' own timezone files are; which implies that get_share_directory() is returning /usr/share; which does not make a lot of sense. I think you must have used nondefault configuration settings for the installation location (--prefix and friends) ... so the above answer is not very helpful. |
#7
| |||
| |||
|
|
As best I can tell, this is coming out because pgtz.c thinks that /usr/share/timezone is where Postgres' own timezone files are; which implies that get_share_directory() is returning /usr/share; which does not make a lot of sense. Nope: $ ./configure --with-perl --with-odbc One nonstandard thing about the target locations was that /usr/local/pgsql is a mount and not an ordinary directory. Dunno how that could make PG lose the libdir, though. |
#8
| |||
| |||
|
|
This is fundamentally broken by the changes to support relocatable installs: PG now attempts to find the support files by relative paths from the place where the executable was found. |
#9
| |||
| |||
|
|
What it looks like is that the postmaster was executed out of /usr/bin. Have you got any symlinks you aren't telling us about? =C2=A0Where does t= hat mount point to, anyway? |
#10
| |||
| |||
|
|
This is fundamentally broken by the changes to support relocatable installs: PG now attempts to find the support files by relative paths from the place where the executable was found. |
![]() |
| Thread Tools | |
| Display Modes | |
| |