| From: | "Zeugswetter Andreas ADI SD" <Andreas(dot)Zeugswetter(at)s-itsolutions(dot)at> |
|---|---|
| To: | "Simon Riggs" <simon(at)2ndquadrant(dot)com>, "Josh Berkus" <fuzzy(at)agliodbs(dot)com> |
| Cc: | <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: WORM and Read Only Tables (v0.1) |
| Date: | 2007-12-12 11:58:11 |
| Message-ID: | E1539E0ED7043848906A8FF995BDA579029CA5A1@m0143.s-mxs.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Getting partitioning/read-only right will allow 70+TB of that to be on
> tape or similar, which with compression can be reduced to maybe 20TB?
I
> don't want to promise any particular compression ratio, but it will
make
> a substantial difference, as I'm sure you realise.
Wouldn't one very substantial requirement of such storage be to
have it independent of db version, or even db product? Keeping
old hardware and software around can be quite expensive.
So, wouldn't a virtual table interface be a better match for such a
problem ? Such a virtual table should be allowed to be part of a
partitioning
scheme, have native or virtual indexes, ...
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2007-12-12 12:20:01 | Re: Slow PITR restore |
| Previous Message | Simon Riggs | 2007-12-12 11:30:25 | Re: Slow PITR restore |