From: Tom Lane <tgl@sss.pgh.pa.us>
To: Joshua D. Drake <jd@commandprompt.com>
Cc: Gregory Stark <stark@enterprisedb.com>
Cc: Simon Riggs <simon@2ndquadrant.com>
Cc: Bernd Helmle <mailings@oopsware.de>
Cc: mfatticcioni@mbigroup.it
Cc: pgsql-performance@postgresql.org
Subject: Re: DRBD and Postgres: how to improve the perfomance?
Date: Sat, 08 Sep 2007 12:39:37 -0400
Message-ID: <24337.1189269577@sss.pgh.pa.us> (raw)
In-Reply-To: <46E2CAAF.50205@commandprompt.com>
References: <2C070D1C3970467FF64F6B6A@imhotep.credativ.de>
<1189232904.4281.19.camel@ebony.site>
<87k5r1zd52.fsf@oxford.xeocode.com>
<46E2CAAF.50205@commandprompt.com>
"Joshua D. Drake" <jd@commandprompt.com> writes:
> Gregory Stark wrote:
>> "Simon Riggs" <simon@2ndquadrant.com> writes:
>>> You're right, but the distinction is a small one. What are the chances
>>> of losing two independent servers within a few milliseconds of each
>>> other?
>>
>> If they're on the same power bus?
> That chance is minuscule or at least should be.
It seems a bit silly to be doing replication to a slave server that has
any common point of failure with the master.
However, it seems like the point here is not so much "can you recover
your data" as what a commit means. Do you want a commit reported to the
client to mean the data is safely down to disk in both places, or only
one?
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, jd@commandprompt.com, stark@enterprisedb.com, simon@2ndquadrant.com, mailings@oopsware.de, mfatticcioni@mbigroup.it
Subject: Re: DRBD and Postgres: how to improve the perfomance?
In-Reply-To: <24337.1189269577@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox