Received: from maia.hub.org (maia-2.hub.org [200.46.204.251]) by mail.postgresql.org (Postfix) with ESMTP id 6914F1337B8C for ; Mon, 7 Mar 2011 12:10:05 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.251]) (amavisd-maia, port 10024) with ESMTP id 63898-05 for ; Mon, 7 Mar 2011 16:09:57 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from spinlock.commandprompt.com (host-215.commandprompt.net [207.173.203.215]) by mail.postgresql.org (Postfix) with ESMTP id 480141337B4E for ; Mon, 7 Mar 2011 12:09:56 -0400 (AST) Received: from localhost (localhost [127.0.0.1]) by spinlock.commandprompt.com (Postfix) with ESMTP id 56A7D348024; Mon, 7 Mar 2011 08:09:55 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at commandprompt.com Received: from spinlock.commandprompt.com ([127.0.0.1]) by localhost (spinlock.commandprompt.com.commandprompt.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id qC7xBUheLESZ; Mon, 7 Mar 2011 08:09:53 -0800 (PST) Received: from perhan.alvh.no-ip.org (unknown [190.95.20.220]) by spinlock.commandprompt.com (Postfix) with ESMTPSA id 0CCCF348022; Mon, 7 Mar 2011 08:09:53 -0800 (PST) Received: by perhan.alvh.no-ip.org (Postfix, from userid 1000) id B1F296E426; Mon, 7 Mar 2011 13:09:49 -0300 (CLST) Content-Type: text/plain; charset=UTF-8 Cc: Heikki Linnakangas , Aidan Van Dyk , Simon Riggs , pgsql-hackers Subject: Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled synchronous replication. From: Alvaro Herrera To: Andrew Dunstan In-reply-to: <4D74FF15.1070804@dunslane.net> References: <4D741441.2090704@dunslane.net> <1299454125.1696.6138.camel@ebony> <4D74896C.5030402@enterprisedb.com> <4D74DDFA.70800@dunslane.net> <4D74E584.7080409@enterprisedb.com> <4D74E9FA.7070202@dunslane.net> <4D74F3AE.9000802@dunslane.net> <4D74FDEC.5040406@enterprisedb.com> <4D74FF15.1070804@dunslane.net> Date: Mon, 07 Mar 2011 13:09:49 -0300 Message-Id: <1299513979-sup-1987@alvh.no-ip.org> User-Agent: Sup/git Content-Transfer-Encoding: 8bit X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=2.419 tagged_above=-5 required=5 tests=BAYES_00=-1.9, FS_REPLICA=3.599, SARE_SPEC_REPLICA=0.72 X-Spam-Level: ** X-Archive-Number: 201103/474 X-Sequence-Number: 183724 Excerpts from Andrew Dunstan's message of lun mar 07 12:51:49 -0300 2011: > > On 03/07/2011 10:46 AM, Heikki Linnakangas wrote: > > Hmm, I've read that wikipedia definition before, but the "atomic" part > > never caught my eye. You do get zero data loss with what we have; if a > > meteor strikes the master, no acknowledged transaction is lost. I find > > that definition a bit confusing. > > Maybe it is - I agree the difference might be small. I'm just trying to > make sure we don't use a term that could mislead reasonable people about > what we're providing. If we're satisfied that we aren't, then keep it. I think these terms are used inconsistenly enough across the industry that what would make the most sense would be to use the common term and document accurately what we mean by it, rather than relying on some external entity's definition, which could change (like wikipedia's). -- Álvaro Herrera The PostgreSQL Company - Command Prompt, Inc. PostgreSQL Replication, Consulting, Custom Development, 24x7 support