From: | Santiago DIEZ <santiago(dot)diez(at)caoba(dot)fr> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL LIST <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Change Unix Socket directory at build time |
Date: | 2017-04-14 17:12:23 |
Message-ID: | CAJh8RqWWwX18B7aLQxeEYrP_NX4+5X+Up6qPY_-gD92FzF4B6w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
no no, if I set -t to 60 seconds (or even 1000), it's the same problem.
-------------------------
Santiago DIEZ
Quark Systems & CAOBA
23 rue du Buisson Saint-Louis, 75010 Paris
-------------------------
On Fri, Apr 14, 2017 at 7:05 PM, David G. Johnston
<david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
> On Fri, Apr 14, 2017 at 9:43 AM, Santiago DIEZ <santiago(dot)diez(at)caoba(dot)fr>
> wrote:
>>
>> To be fully transparent, the issue I'm dealing with is the following:
>> If I set a specific unix_socket_directory in postgresql.conf then running
>> pg_ctl start -w -t5 -D '/val/lib/postgresql/9.4/main'
>> fails because I believe it cannot verify the server is running because
>> it's looking for socket in /tmp.
>
>
> More likely is that it takes more than 5 seconds to start and you are timing
> out. (I'll presume */val* is a typo in the email only)
>
> The source code for pg_ctl indicates that the "pid file" the postmaster
> creates at startup contains the information needed for both unix and tcp
> socket connections and this is where pg_ctl gets its "connection string"
> information from.
>
> Supplying logging data from the pg_ctl run would help.
>
> David J.
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2017-04-14 17:40:41 | Re: Change Unix Socket directory at build time |
Previous Message | David G. Johnston | 2017-04-14 17:05:46 | Re: Change Unix Socket directory at build time |