Thread: Creating Multiple Instance
Hi All,
We are planning to create a 2nd instance of postgres db in the same server. The reason is simple. After we added another application, the number of WAL(s) created is too much. So we want to separate the db by moving it out to another instance of postgres in the same machine. We want to study that new application the new db independently to understand what could go wrong. Meanwhile we want the operations and backups on our existing db running on 5432 port to be going on as usual.
Steps we took:
1.Create a new cluster "/pgs/903/data_5433"
2. Start the db instance using new parameters i.e. - (su - postgres -c "/opt/pgs/903/bin/pg_ctl -w start -D \"/pgs/903/data_5433\" -l \"/pgs/903/data_5433/pg_log/startup.log\"")
Unfortunately we got the following error.
pg_ctl: another server might be running; trying to start server anyway
waiting for server to start... done
server started
First of all, we want to know if at all it is possible to do this in PostgreSQL, or whether we missed out any important steps.
Please help.
Thank you.
Regards,
Selvam
Hi, thats possible. Dont forget so set another port in your postgresql.conf Thomas Am 13.12.2011 09:23, schrieb Selva manickaraja: > Hi All, > > We are planning to create a 2nd instance of postgres db in the same > server. The reason is simple. After we added another application, the > number of WAL(s) created is too much. So we want to separate the db by > moving it out to another instance of postgres in the same machine. We > want to study that new application the new db independently to > understand what could go wrong. Meanwhile we want the operations and > backups on our existing db running on 5432 port to be going on as usual. > > Steps we took: > > 1.Create a new cluster "/pgs/903/data_5433" > 2. Start the db instance using new parameters i.e. - (su - postgres -c > "/opt/pgs/903/bin/pg_ctl -w start -D \"/pgs/903/data_5433\" -l > \"/pgs/903/data_5433/pg_log/startup.log\"") > > Unfortunately we got the following error. > > pg_ctl: another server might be running; trying to start server anyway > waiting for server to start... done > server started > > First of all, we want to know if at all it is possible to do this in > PostgreSQL, or whether we missed out any important steps. > > Please help. > > Thank you. > > Regards, > > Selvam > >
Thomas Markus <t.markus@proventis.net> writes: > thats possible. Dont forget so set another port in your postgresql.conf I think actually the reason pg_ctl is complaining is that it doesn't know how to read postgresql.conf, so it's unaware that the second server is supposed to be on 5433. (IIRC, this is fixed in 9.1, but not 9.0.) It is starting the postmaster correctly, but the -w switch likely doesn't work as expected. What I'd suggest is setting the nondefault port number both in postgresql.conf and on the server command line --- ie, if you're using pg_ctl, include -o '-p 6433' in its arguments. That tells pg_ctl what's going on, and it has another benefit that you'll soon recognize: you'll be able to tell which postmaster is which in ps listings. The postgresql.conf entry is then redundant, but a good thing to have as a backstop in case you forget the command line switch one day. regards, tom lane
On Tue, Dec 13, 2011 at 1:23 AM, Selva manickaraja <mavles78@gmail.com> wrote: > Hi All, > > We are planning to create a 2nd instance of postgres db in the same server. > The reason is simple. After we added another application, the number of You don't mention which OS you're running, but any debian based Linux distro can do this rather easily with pg_createcluster.