From: | "Mark Woodward" <pgsql(at)mohawksoft(dot)com> |
---|---|
To: | "Rick Gigger" <rick(at)alpinenetworking(dot)com> |
Cc: | "Chris Campbell" <chris(at)bignerdranch(dot)com>, "Mark Woodward" <pgsql(at)mohawksoft(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Multiple logical databases |
Date: | 2006-02-03 20:28:54 |
Message-ID: | 16578.24.91.171.78.1138998534.squirrel@mail.mohawksoft.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
>
> On Feb 3, 2006, at 6:47 AM, Chris Campbell wrote:
>
>> On Feb 3, 2006, at 08:05, Mark Woodward wrote:
>>
>>> Using the "/etc/hosts" file or DNS to maintain host locations for
>>> is a
>>> fairly common and well known practice, but there is no such
>>> mechanism for
>>> "ports." The problem now becomes a code issue, not a system
>>> administration
>>> issue.
>>
>> What if you assigned multiple IPs to a machine, then used ipfw (or
>> something) to forward connections to port 5432 for each IP to the
>> proper IP and port?
>
> If he had multiple ips couldn't he just make them all listen only on
> one specific ip (instead of '*') and just use the default port?
That is a good idea, and yes it would work, as do a lot of other
scenarios, but shouldn't PostgreSQL take care of "PostgreSQL?"
From | Date | Subject | |
---|---|---|---|
Next Message | Mark Dilger | 2006-02-03 21:01:01 | Re: Function Stats WAS: Passing arguments to views |
Previous Message | Mark Woodward | 2006-02-03 20:26:29 | Re: Multiple logical databases |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2006-02-03 21:15:32 | Re: psql tab completion enhancements |
Previous Message | Joachim Wieland | 2006-02-03 20:26:48 | Re: psql tab completion enhancements |