From: | Adrian Klaver <aklaver(at)comcast(dot)net> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Cc: | Josef Wolf <jw(at)raven(dot)inka(dot)de> |
Subject: | Re: pg_ctl with unix domain socket? |
Date: | 2009-09-04 00:16:56 |
Message-ID: | 200909031716.56959.aklaver@comcast.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thursday 03 September 2009 12:20:02 pm Josef Wolf wrote:
> On Tue, Sep 01, 2009 at 04:47:25PM +0200, Josef Wolf wrote:
> > On Tue, Sep 01, 2009 at 06:34:21AM -0700, Adrian Klaver wrote:
> > > On Tuesday 01 September 2009 4:28:22 am Josef Wolf wrote:
> >
> > [ ... ]
> >
> > > > Any hints how to use pg_ctl to start/stop postgresql on a unix domain
> > > > socket?
> > >
> > > 1) In postgresql.conf make listen_addresses empty per instructions:
> >
> > I could get it running with putting listen_addresses='' in
> > postgresql.conf and then running
>
> BTW: it works fine without the listen_address='' setting in postgresql.conf
>
> > pg_ctl -Ddb -o "-h '' -k `pwd`/db" -l postgreslog start
>
> This works, but when I add the -w option, it waits all the 60 seconds. So
> for some reason, pg_ctl does not notice that postgres is ready to accept
> connections. This problem seems to happen only when starting. Stopping
> works immediately.
>
> Any ideas?
My playing around with this seems to indicate that the -k switch is causing the
problem. Changing the default location of the socket seems to throw things off.
--
Adrian Klaver
aklaver(at)comcast(dot)net
From | Date | Subject | |
---|---|---|---|
Next Message | 纪晓曦 | 2009-09-04 01:02:20 | trick problem |
Previous Message | Stephen Frost | 2009-09-04 00:10:44 | Re: column level, uid based authorization to update columns |