Received: from maia.hub.org (unknown [200.46.204.251])
	by mail.postgresql.org (Postfix) with ESMTP id 5CEE21337B50
	for <pgsql-hackers-postgresql.org@mail.postgresql.org>;
	Thu, 21 Oct 2010 21:46:35 -0300 (ADT)
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 73556-07
	for <pgsql-hackers-postgresql.org@mail.postgresql.org>;
	Fri, 22 Oct 2010 00:46:27 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from glacier.frostconsultingllc.com (glacier.frostconsultingllc.com
	[69.36.227.170])
	by mail.postgresql.org (Postfix) with ESMTP id 972BD1337B66
	for <pgsql-hackers@postgresql.org>;
	Thu, 21 Oct 2010 21:46:26 -0300 (ADT)
Received: from dsl081-245-111.sfo1.dsl.speakeasy.net ([64.81.245.111]
	helo=Sidney-Stratton.local)
	by glacier.frostconsultingllc.com with esmtpsa
	(TLSv1:CAMELLIA256-SHA:256) (Exim 4.69)
	(envelope-from <josh@agliodbs.com>)
	id 1P95m2-0007OL-CO; Thu, 21 Oct 2010 17:46:24 -0700
Message-ID: <4CC0DEDE.7060707@agliodbs.com>
Date: Thu, 21 Oct 2010 17:46:22 -0700
From: Josh Berkus <josh@agliodbs.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US;
	rv:1.9.1b3pre) Gecko/20090223 Thunderbird/3.0b2
MIME-Version: 1.0
To: Bruce Momjian <bruce@momjian.us>
CC: Greg Stark <gsstark@mit.edu>, pgsql-hackers@postgresql.org
Subject: Re: Simplifying replication
References: <201010220022.o9M0M8Q29438@momjian.us>
In-Reply-To: <201010220022.o9M0M8Q29438@momjian.us>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit
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: 201010/1608
X-Sequence-Number: 172648


> Agreed, but as a reality check:  when I proposed that wal_keep_segments
> = -1 would keep all WAL segments (for use while the file system was
> being backed up), I was told administrators shoud compute how much free
> disk space they had.  Obviously easy of use is not our #1 priority.

Depends.  Running out of disk space isn't exactly user-friendly either.
 And detecting how much free space is available would be a painful bit
of platform-dependant code ...

-- 
                                  -- Josh Berkus
                                     PostgreSQL Experts Inc.
                                     http://www.pgexperts.com