Re: [GENERAL] Multiple postgresql installations on one machine.

2001-10-13 Thread Tom Lane 

Charles Tassell [EMAIL PROTECTED] writes:
 I may be wrong, but I don't think it's possible to have them on the same 
 port.  The problem is that the TCP/IP port defaults to the same as the UNIX 
 sockets port, and UNIX sockets are local to the machine, so they are 
 completely independent of IP addresses and can not be duplicated.

Unix sockets need to have unique pathnames in the local filesystem.
The PG port number is actually only a component of the file name.
So all you need to do if you need to have conflicting port numbers
is to vary the unix_socket_directory parameter for each postmaster.

However, varying the port number is probably a simpler attack...

 I can't seem to tell psql where to find the moved unix socket.

Use -h /path/to/directory/containing/socket.  AFAIR you can set the
path in PGHOST environment variable, if that helps.

regards, tom lane

---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly

Re: [GENERAL] Multiple postgresql installations on one machine.

2001-10-13 Thread Lincoln Yeoh 

Thanks. I didn't know psql -h did that, thought it was for hostnames only :).

So I resorted to TCP access for the rest of the installations and moved the
sockets out of the way. However the Redhat style initscript tends to
shutdown all installations - even though I specified a different PID file
:(. I guess I might need to fix that one - coz the idea is to have them
independent.

Was actually wondering if I could change the name of the socket to
something like ...portnumber.virtual_host_name_or_ip_address

That way psql -h vhost1 would try usualprefix.defaultport.vhost1

psql by itself would try usualprefix.defaultport

(have to convert dots and slashes in addresses to underscores or something
more innocuous, or quote carefully)

Probably not that useful now that I know more about -h :).

Cheerio,
Link.
 
At 12:03 AM 10/13/01 -0400, Tom Lane wrote:
Charles Tassell [EMAIL PROTECTED] writes:
 I may be wrong, but I don't think it's possible to have them on the same 
 port.  The problem is that the TCP/IP port defaults to the same as the
UNIX 
 sockets port, and UNIX sockets are local to the machine, so they are 
 completely independent of IP addresses and can not be duplicated.

Unix sockets need to have unique pathnames in the local filesystem.
The PG port number is actually only a component of the file name.
So all you need to do if you need to have conflicting port numbers
is to vary the unix_socket_directory parameter for each postmaster.

However, varying the port number is probably a simpler attack...

 I can't seem to tell psql where to find the moved unix socket.

Use -h /path/to/directory/containing/socket.  AFAIR you can set the
path in PGHOST environment variable, if that helps.

   regards, tom lane

---(end of broadcast)---
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly




---(end of broadcast)---
TIP 6: Have you searched our list archives?

http://archives.postgresql.org

[GENERAL] Multiple postgresql installations on one machine.

2001-10-12 Thread Lincoln Yeoh 

Hi,

Is it possible to have multiple postgresql installations on one machine
running on the same port but on different IP addresses?

I've specified different IPs/hostnames for the virtual_host but the unix
socket clashes when I try. 

Should I just move the unix sockets somewhere else with -k, what would the
impact be? I can't seem to tell psql where to find the moved unix socket.

Cheerio,
Link.





---(end of broadcast)---
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/users-lounge/docs/faq.html