From: | Josef Wolf <jw(at)raven(dot)inka(dot)de> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: pg_ctl with unix domain socket? |
Date: | 2009-09-01 12:34:00 |
Message-ID: | 20090901123400.GA19919@raven.wolf.lan |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, Sep 01, 2009 at 05:28:46PM +0530, Abbas wrote:
> On Tue, Sep 1, 2009 at 4:58 PM, Josef Wolf <jw(at)raven(dot)inka(dot)de> wrote:
Thanks for your fast response, Abbas!
> > I have created a fresh cluster with
> > initdb -D /some/path/pgtest
> > PGPORT=/some/path/pgtest pg_ctl -D/some/path/pgtest -l postgreslog start
>
> PGPORT should be the port number on which the Postgresql server is
> running(5432 is default), and PGDATA=some/path/pgtest .
Yeah, I see. But I do not want it to bind to network socket. I want it to
bind to a unix domain socket _only_.
While all other postgres commands accept an absolute path as port
specification, meaning to use a unix domain socket, pg_ctl seems to behave
differently.
e.g: I can start postgres on a unix domain socket _only_ with following
parameters:
postgres -D /some/path/pgtest -h '' -k /some/path/pgtest
But pg_ctl don't seem to have an option to do the same.
From | Date | Subject | |
---|---|---|---|
Next Message | Raymond O'Donnell | 2009-09-01 12:49:12 | Re: Query and the number of row result |
Previous Message | Abbas | 2009-09-01 11:58:46 | Re: pg_ctl with unix domain socket? |