From: | Christopher Browne <cbbrowne(at)acm(dot)org> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: postgresql replication |
Date: | 2005-05-05 20:28:22 |
Message-ID: | m3y8atct95.fsf@knuth.cbbrowne.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Centuries ago, Nostradamus foresaw when smarlowe(at)g2switchworks(dot)com (Scott Marlowe) would write:
> On Wed, 2005-05-04 at 21:06, Vlad wrote:
>> the number one aim at the moment is to have "always-up-to-date" copy
>> of our main DB with minial performance impact on replication
>
> Have you considered point in time recovery as implemented in 8.0?
>
> While it does require some small amount of work to bring the secondary
> server up to date, it's not that much, and it gives you very up to date
> recoverability.
If they want to be able to use the replica, perhaps to run reports on
it, that turns out to be problematic.
--
select 'cbbrowne' || '@' || 'cbbrowne.com';
http://linuxfinances.info/info/spreadsheets.html
Long computations which yield zero are probably all for naught.
From | Date | Subject | |
---|---|---|---|
Next Message | Ying Lu | 2005-05-05 20:37:58 | "current transaction is aborted, commands ignored until end of transaction block" Error |
Previous Message | A. Mous | 2005-05-05 19:47:43 | Re: Postmaster not reporting number of connections correctly |