Re: Feature suggestion: Postgresql binding to one IP?

Hi Lincoln,

Not sure why you would want to run multiple instances, since you can run
multiple dbs if you want to maintain separate environments but if you really
need to do this, the postmaster has some options which control ip/port
binds:

[pritchma@blade pritchma]$ /usr/local/pgsql/bin/postmaster --help
/usr/local/pgsql/bin/postmaster is the PostgreSQL server.

Usage: /usr/local/pgsql/bin/postmaster [options...]

Options: -B NBUFFERS     number of shared buffers (default 64) -c NAME=VALUE   set run-time parameter -d 1-5
debugginglevel -D DATADIR      database directory -F              turn fsync off -h HOSTNAME     host name or IP
addressto listen on -i              enable TCP/IP connections -k DIRECTORY    Unix-domain socket location -N
MAX-CONNECT maximum number of allowed connections (1..1024, default
 
32) -o OPTIONS      pass 'OPTIONS' to each backend server -p PORT         port number to listen on (default 5432) -S
         silent mode (start in background without logging output)
 

Developer options: -n              do not reinitialize shared memory after abnormal exit -s              send SIGSTOP
toall backend servers if one dies
 

I run postgres on a box with two interfaces, and I only want it to bind to a
single one:

# start postgres
nohup > /dev/null su -c '/usr/local/pgsql/bin/postmaster -h 10.4.0.1 -i -D
/usr/local/pgsql/data > /usr/local/pgsql/log/server.log 2>&1' postgres &


Cheers,

Mark Pritchard