From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Josef Wolf <jw(at)raven(dot)inka(dot)de> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: pg_ctl with unix domain socket? |
Date: | 2009-09-06 14:34:04 |
Message-ID: | 22996.1252247644@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Josef Wolf <jw(at)raven(dot)inka(dot)de> writes:
> On Fri, Sep 04, 2009 at 01:33:06PM -0400, Tom Lane wrote:
>> In general I'd advise against using -k, as that will break nearly all
>> clients not only pg_ctl.
> Ugh, but how to configure it at runtime, then?
You don't. You could configure it at build time, perhaps, same as you
configure the installation prefix path --- but you're just creating
unnecessary pain for yourself.
> The goal I want to achieve is to get testing/development environments for
> rails with postgres relative to the working copy of the checked out
> directory. Not having this relative prevents multiple working copies
> to run tests in parallel because they all would use the same database.
The standard way to run multiple installations in parallel is to run
them on different port numbers. There is no reason to move the socket
directory.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Richard Greenwood | 2009-09-06 14:51:31 | tsearch synonym dictionary problem |
Previous Message | Jerry LeVan | 2009-09-06 14:31:43 | More Snow Leopard problems... |