|
From: Ben C. <ben...@gm...> - 2011-01-08 06:55:21
|
I am interested in turning my 'public' netdisco server - which receives full database dumps from the 'private' server - into a slave and enabling postgres 9.0's new hot standby feature. This feature forces slave databases into a read-only state. The only sticking points I can see is that the slave will attempt to write logon information from the web interface, as well as the batch job logs. Is there a (relatively easy) way to get netdisco on the slave to write to the master database but continue to read from itself? I also would be interested to hear if anyone has yet tried to get netdisco working in a hot standby setup. cheers, B |