Hello All,
Issue can be closed, found the solution, sorry for disturbance.
Thanks, Tom, for an attempt, but actually the issue was in 3 things of postgresql:
1. /tmp/.s.**** and /var/run/postgresql ownage and chmod settings. (+ pid deleting if not helping and killing all (theoretically) running servers by reported ports.)
2. The server is meant to be started by postgres user, not '-u postgres' . (Don't know why, it just is so... Took long time to figure it out, would be great if someone can give a logical explanation.)
3. Database must by initiated by postgres, and chmod settings of global/pg_filenode.map should be checked. (Default were misconfigured in Debian...)
P.S. /usr/bin/psql is recommended install dir by guide if building postgresql from sources, or using distributed package manager.
P.P.S. Just in case someone used guide, and this solution didn't help to fix the issue, extrainfo: Manual build was installed to other than recommended place ( to avoid messing with package manager.), so extraissues are possible.
--
Lex
Mon, 15 Dec 2014 20:19:38 -0500 от Tom Lane <tgl@sss.pgh.pa.us>:
aleks.dark@inbox.ru writes:
> Similar error to case in 2011, but this time no upgrade available. Any hints
> what is going wrong?
> Use of uninitialized value $lib_path in concatenation (.) or string at
> /usr/bin/psql line 132.
> psql (PostgreSQL) 9.3.5
> $ ldd /usr/lib/postgresql/9.3/bin/psql
Note that the complaint is specifically about /usr/bin/psql, not
/usr/lib/postgresql/9.3/bin/psql.
I would guess that /usr/bin/psql is a Perl script that is supposed to
invoke the real psql but is going off the rails somehow. You will need
to speak with whoever produced the PG package you're using, because any
such script would've been supplied by the packager, not by the Postgres
community.
regards, tom lane