Re: Per-database warm standby?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I also have a question about warm standby replication.
What'd be the best solution for the system with 2 db servers (nodes), 1 database and 10 seconds max to switch between them (ready to switch time). Currently I'm using Slony, but it's kind of slow when doing subscribe after failover on the failed node (database can be really huge and it would take a few hours to COPY tables using Slony).
May be WAL replication would be better?

Best regards, Nick.

Tom Lane wrote:
Craig James <craig_james@xxxxxxxxxxxxxx> writes:
8.4 has vastly improved the warm-standby features, but it looks to me like this is still an installation-wide backup, not a per-database backup.  That is, if you have (say) a couple hundred databases, and you only want warm-backup on one of them, you can't do it (except using other solutions like Slony).  Is that right?

Correct, and that's always going to be true of any WAL-based solution.

			regards, tom lane


--
Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance

[Postgresql General]     [Postgresql PHP]     [PHP Users]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Yosemite]

  Powered by Linux