X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 7F1E4D1EBC5 for ; Sat, 20 Mar 2004 13:24:30 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 35410-10 for ; Sat, 20 Mar 2004 09:24:27 -0400 (AST) Received: from news.hub.org (news.hub.org [200.46.204.72]) by svr1.postgresql.org (Postfix) with ESMTP id 2654CD1EB02 for ; Sat, 20 Mar 2004 09:24:24 -0400 (AST) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.12.9/8.12.9) with ESMTP id i2KDON1Y090845 for ; Sat, 20 Mar 2004 13:24:23 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.12.9/8.12.9/Submit) id i2KDCnYE089752 for pgsql-admin@postgresql.org; Sat, 20 Mar 2004 13:12:49 GMT Date: Sat, 20 Mar 2004 08:12:02 -0500 From: Al Cohen User-Agent: Mozilla Thunderbird 0.5 (Windows/20040207) X-Accept-Language: en-us, en MIME-Version: 1.0 X-Newsgroups: comp.databases.postgresql.admin Subject: Restoring DB From A Log? Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Message-ID: <_8GcnZrZwrXI3sHdRWPC-g@speakeasy.net> Lines: 21 X-Complaints-To: abuse@speakeasy.net X-DMCA-Complaints-To: abuse@speakeasy.net X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly X-Postfilter: 1.1 To: pgsql-admin@postgresql.org X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200403/279 X-Sequence-Number: 12848 We've been using PostgreSQL for some time, and it's been very, very reliable. However, we're starting to think about preparing for something bad happening - dead drives, fires, locusts, and whatnot. In our particular situation, being down for two hours or so is OK. What's really bad is losing data. The PostgreSQL replication solutions that we're seeing are very clever, but seem to require significant effort to set up and keep going. Since we don't care if a slave DB is ready to kick over at a moment's notice, I'm wondering if there is some way to generate data, in real time, that would allow an offline rebuild in the event of catastrophe. We could copy this data across the 'net as it's available, so we could be OK even if the place burned down. Is there a log file that does or could do this? Or some internal system table that we could use to generate something? Thanks! Al Cohen