Re: Strange behaviour with Xfs filesystem and unix_socket_directory

From: Denis Gasparin <denis(at)edistar(dot)com>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: Strange behaviour with Xfs filesystem and unix_socket_directory
Date: 2007-07-24 16:09:59
Message-ID: 46A62457.6010503@edistar.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


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(at)edistar(dot)com> 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(at)postgresql(dot)org so that your
> message can get through to the mailing list cleanly
>
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Joshua D. Drake 2007-07-24 16:12:17 Re: Using result from current_database() into another command?
Previous Message Raymond O'Donnell 2007-07-24 16:02:09 Re: Connection error