| From: | "Peter Childs" <peterachilds(at)gmail(dot)com> |
|---|---|
| To: | |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: WORM and Read Only Tables (v0.1) |
| Date: | 2007-12-11 13:54:12 |
| Message-ID: | a2de01dd0712110554y35282ee9s1e864c3f594e129b@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 11/12/2007, Csaba Nagy <nagy(at)ecircle-ag(dot)com> wrote:
>
> On Tue, 2007-12-11 at 14:58 +0200, Hannu Krosing wrote:
> > Ühel kenal päeval, T, 2007-12-11 kell 13:44, kirjutas Csaba Nagy:
> > >> Then put the active chunk on a high performance file system and the
> > > archive tablespace on a compressed/slow/cheap file system and you're
> > > done. Allow even the archive chunk to be updateable, and put new tuple
> > > data in the active chunk. It would work just fine for cases where the
> > > old data is rarely updated/deleted...
> >
> > You can't update a table on a read-only (write-once) partition, at least
> > not with current header structure.
>
> OK, but that's what I'm challenging, why do you need a write once
> partition ? You mean by that tapes ? OK, it means I was thinking in
> completely different usage scenarios then...
>
> Cheers,
> Csaba.
>
>
>
I think DVD or CD would make sence, Tapes have an added limitation of being
sequential access only.
Peter Childs
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Childs | 2007-12-11 14:07:40 | Re: WORM and Read Only Tables (v0.1) |
| Previous Message | Trevor Talbot | 2007-12-11 13:50:46 | Re: WORM and Read Only Tables (v0.1) |