pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Chris Browne <cbbrowne@acm.org>
To: pgsql-admin@postgresql.org
Subject: Re: [GENERAL] Storing database in WORM devices
Date: Wed, 11 May 2005 18:47:13 -0400
Message-ID: <60is1ptm6m.fsf@dba2.int.libertyrms.com> (raw)
References: <E8C21173A4ACCF48BEAB8DA3ABE46F24093807@mailsrv1.ctronsoft.com>
	<20050511203227.GA8262@uiuc.edu>
	<9e0a28690505111340324940ef@mail.gmail.com>

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.''"
<http://www.eviloverlord.com/;



view thread (12+ messages)

Message-ID: <60is1ptm6m.fsf@dba2.int.libertyrms.com>
Permalink:  ../60is1ptm6m.fsf@dba2.int.libertyrms.com/
Also on:    postgresql.org/message-id/60is1ptm6m.fsf@dba2.int.libertyrms.com

 · 

reply

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 from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: cbbrowne@acm.org
  Subject: Re: [GENERAL] Storing database in WORM devices
  In-Reply-To: <60is1ptm6m.fsf@dba2.int.libertyrms.com>
  References: <E8C21173A4ACCF48BEAB8DA3ABE46F24093807@mailsrv1.ctronsoft.com> <20050511203227.GA8262@uiuc.edu> <9e0a28690505111340324940ef@mail.gmail.com> <60is1ptm6m.fsf@dba2.int.libertyrms.com>

* 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