Hi,
Our IT budget is not so much and even so I´m trying to set up a
Postgresql high availability solution for our business.
My managers gave me the following statements that I must follow:
. the system could be out of service no more than 2 hours
. last 5 minutes of work could be lost
The fi
Slony is a good choice... but the ERP owner will charge us a lot to include primary keys or unique not null columns all over the system. Philippe Ferreira <[EMAIL PROTECTED]> escreveu: Hi,> Another cheap alternative is diarly (00:00) stop the master database > and make a copy of the $PGDATA di
Hi,
Another cheap alternative is diarly (00:00) stop the master database
and make a copy of the $PGDATA directory to the slave and during the
day make regularly (5 x 5 minutes) copies of the current wal file to
the slave too.
To recover the system we need only to apply all the logs created
Hi, Our IT budget is not so much and even so I´m trying to set up a Postgresql high availability solution for our business. My managers gave me the following statements that I must follow: . the system could be out of service no more than 2 hours. last 5 minutes of work could be lost The
