X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id A226D53C91 for ; Wed, 11 May 2005 20:13:07 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 10018-08 for ; Wed, 11 May 2005 23:12:58 +0000 (GMT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by svr1.postgresql.org (Postfix) with ESMTP id DBFD853497 for ; Wed, 11 May 2005 20:12:57 -0300 (ADT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.13.1/8.13.1) with ESMTP id j4BNCvLO012326 for ; Wed, 11 May 2005 23:12:57 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.13.1/8.13.1/Submit) id j4BN3xH6011041 for pgsql-admin@postgresql.org; Wed, 11 May 2005 23:03:59 GMT (envelope-from news) From: Chris Browne X-Newsgroups: pgsql.admin Subject: Re: [GENERAL] Storing database in WORM devices Date: Wed, 11 May 2005 18:47:13 -0400 Organization: cbbrowne Computing Inc Lines: 27 Message-ID: <60is1ptm6m.fsf@dba2.int.libertyrms.com> References: <20050511203227.GA8262@uiuc.edu> <9e0a28690505111340324940ef@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Complaints-To: usenet@news.hub.org User-Agent: Gnus/5.1006 (Gnus v5.10.6) XEmacs/21.4 (Jumbo Shrimp, linux) Cancel-Lock: sha1:FfePD8qft2q1QvjWUOb+1lRWWPw= To: pgsql-admin@postgresql.org X-Virus-Scanned: by amavisd-new at hub.org X-Archive-Number: 200505/140 X-Sequence-Number: 17569 juan.paredes@gmail.com (Juan Miguel Paredes) writes: > I know it would be a hard approach but... perhaps ON DELETE and ON > UPDATE triggers would help? No, that's not even related to the real problem. The problem is that the ability to have transactions is deeply pervasive, and requires a writable store even though you don't imagine you're doing updates to the data. Version 8 probably moves this closer to reality with the addition of tablespace support. Using that, you could take "finished" tables, and put them into a particular tablespace. VACUUM FREEZE them to pretty well eliminate the need to touch them again. Then take that tablespace offline, turn it into a CDROM, and mount it back in the same location. If you do all that, and make the entire tablespace read-only, I could imagine it sorta working. Though I wouldn't want to bet money on the outcome, at this point... -- (format nil "~S@~S" "cbbrowne" "acm.org") http://www.ntlug.org/~cbbrowne/sap.html Rules of the Evil Overlord #78. "I will not tell my Legions of Terror "And he must be taken alive!" The command will be: ``And try to take him alive if it is reasonably practical.''"