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 <[EMAIL PROTECTED]> writes:
>
>> We configured the unix_socket_directory in postgresql.
Denis Gasparin <[EMAIL PROTECTED]> 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 postgr
We configured the unix_socket_directory in postgresql.conf to point to a
folder in a xfs filesystem.
The problem is that pg_ctl tries to start the daemon but after 1 minute
it gives up with the following message: could not start postmaster.
The strange thing is that the postmaster is there, up an
