Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: DRDB risk factors?
- From: Hannes Dorbath <light(at)theendofthetunnel(dot)de>
- To: Kevin Kempter <kevin(at)kevinkempterllc(dot)com>
- To: pgsql-general(at)postgresql(dot)org
- Subject: Re: DRDB risk factors?
- Date: Thu, 31 May 2007 09:31:58 +0200
On 30.05.2007 23:31, Kevin Kempter wrote:
per considering DRDB as a replication solution in a failed master node scenario, is there a risk of loosing not only in-flight transactions but alos un-sync'd buffer-pool dirty pages?If so, how might I minimize this risk ?
If you have DRBD using protocol C and fsync enabled in PG you don't lose a single commit. That is true for any ACID conform application.
Be sure to you have your hardware right. Running DRBD on fsync/fua lying hardware is committing suicide. I can't stress that enough.
-- Regards, Hannes Dorbath
- References:
- DRDB risk factors?
- From: Kevin Kempter
- DRDB risk factors?
- Prev by Date: Make for PgSQL?
- Next by Date: Re: Make for PgSQL?
- Previous by thread: Re: DRDB risk factors?
- Next by thread: REMOTE CONNECTION
- Indexes: