On Sun, Oct 19, 2008 at 11:21:09PM -0400, Tom Lane wrote:
> Eric Haszlakiewicz <[EMAIL PROTECTED]> writes:
> > On Sun, Oct 19, 2008 at 10:15:22PM -0400, Tom Lane wrote:
> >> What platform is this, anyway?
> > I'm running on NetBSD 4.
>
> > Well, it seems that something doesn't work right with the
Eric Haszlakiewicz <[EMAIL PROTECTED]> writes:
> On Sun, Oct 19, 2008 at 10:15:22PM -0400, Tom Lane wrote:
>> Well, different chroot would do it, but you didn't mention that ;-)
> er.. why does a chroot matter?
Putting the servers in different chroots would mean that they see two
different /tmp
On Sun, Oct 19, 2008 at 10:15:22PM -0400, Tom Lane wrote:
> Eric Haszlakiewicz <[EMAIL PROTECTED]> writes:
> > On Sat, Oct 18, 2008 at 12:48:13PM -0400, Tom Lane wrote:
> >> That's already documented not to work, and not for any hidden
> >> implementation reason: you'd have a conflict on the Unix-d
Eric Haszlakiewicz <[EMAIL PROTECTED]> writes:
> On Sat, Oct 18, 2008 at 12:48:13PM -0400, Tom Lane wrote:
>> That's already documented not to work, and not for any hidden
>> implementation reason: you'd have a conflict on the Unix-domain socket
>> name.
> er.. but I didn't get any kind of error a
On Sat, Oct 18, 2008 at 12:48:13PM -0400, Tom Lane wrote:
> Eric Haszlakiewicz <[EMAIL PROTECTED]> writes:
> > I just spent a couple of days trying to figure out why I couldn't start
> > two servers on the same port, even though I was configuring separate
> > listen_address values.
>
> That's alre
Andrew Dunstan <[EMAIL PROTECTED]> writes:
> Tom Lane wrote:
>> That's already documented not to work, and not for any hidden
>> implementation reason: you'd have a conflict on the Unix-domain socket
>> name.
> unless you use a different socket directory.
Hmm ... but the OP didn't mention any suc
Tom Lane wrote:
Eric Haszlakiewicz <[EMAIL PROTECTED]> writes:
I just spent a couple of days trying to figure out why I couldn't start
two servers on the same port, even though I was configuring separate
listen_address values.
That's already documented not to work, and not for any hi
Eric Haszlakiewicz <[EMAIL PROTECTED]> writes:
> I just spent a couple of days trying to figure out why I couldn't start
> two servers on the same port, even though I was configuring separate
> listen_address values.
That's already documented not to work, and not for any hidden
implementation reas
I just spent a couple of days trying to figure out why I couldn't start
two servers on the same port, even though I was configuring separate
listen_address values. I kept gettting errors about shmget failing with
"could not create shared memory segment: Invalid argument".
I finally noticed that
