From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
---|---|
To: | "Mark Morgan Lloyd" <markMLl(dot)pgsql-general(at)telemetry(dot)co(dot)uk> |
Cc: | <pgsql-general(at)PostgreSQL(dot)org> |
Subject: | Re: Tablespaces on tertiary media |
Date: | 2007-09-14 10:04:09 |
Message-ID: | 87bqc5o95y.fsf@oxford.xeocode.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
"Mark Morgan Lloyd" <markMLl(dot)pgsql-general(at)telemetry(dot)co(dot)uk> writes:
> Where does PostgreSQL stand with storing /really/ large amounts of data
> offline? Specifically, if a FUSE is used to move a tablespace to something like
> a tape archiver can the planner be warned that access might take an extended
> period?
No, Postgres can't deal with this. You'll have to dump the tables with pg_dump
or COPY or something like that and then drop them from the database. If you
need them again you have to load them again.
Actually if the tables are missing but nobody tries to access them (including
autovacuum) then nothing will notice they're missing. But if you do try to
access them you'll get an error. And if you leave it in this situation too
long your database will shut down from getting too close to transaction
wraparound.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Phoenix Kiula | 2007-09-14 10:14:45 | Issue with uninstalling postgres 8.1.9 |
Previous Message | Mark Morgan Lloyd | 2007-09-14 09:06:25 | Tablespaces on tertiary media |