Setting PGHOST solved the problem! It was not clear to me that pg_ctl is actually a client and it doesn't read the configuration from postgresql.conf Thank you, Denis Tom Lane ha scritto: Denis Gasparin <denis@xxxxxxxxxxx> writes:We configured the unix_socket_directory in postgresql.conf to point to a folder in a xfs filesystem.I don't think pg_ctl can deal with nondefault settings of unix_socket_directory, because it does not make any attempt to parse the postmaster's postgresql.conf file. So it's still trying to contact the postmaster in /tmp, and of course not seeing any evidence the postmaster is up. You'll find that most other clients fail similarly. You might be able to make it work if you set PGHOST to the socket directory before running pg_ctl (and other clients). But I think if you really want this, you would be best advised to alter the default socket directory at build time, instead (see DEFAULT_PGSOCKET_DIR in pg_config_manual.h). regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to majordomo@xxxxxxxxxxxxxx so that your message can get through to the mailing list cleanly |