Re: Can't drop tablespace or user after disk gone
- From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
- To: "Craig A. James" <cjames(at)modgraph-usa(dot)com>
- Cc: pgsql-performance(at)postgresql(dot)org
- Subject: Re: Can't drop tablespace or user after disk gone
- Date: Wed, 04 Apr 2007 12:57:13 -0400
- Message-id: <22928(dot)1175705833(at)sss(dot)pgh(dot)pa(dot)us>
"Craig A. James" <cjames(at)modgraph-usa(dot)com> writes:
> I had a 'scratch' database for testing, which I deleted, and then disk went out. No problem, no precious data. But now I can't drop the tablespace, or the user who had that as the default tablespace.
> I thought about removing the tablespace from pg_tablespaces, but it seems wrong to be monkeying with the system tables. I still can't drop the user, and can't drop the tablespace. What's the right way to clear out Postgres when a disk fails and there's no reason to repair the disk?
Probably best to make a dummy postgres-owned directory somewhere and
repoint the symlink at it, then DROP TABLESPACE.
CVS HEAD has recently been tweaked to be more forgiving of such cases...
regards, tom lane
Home |
Main Index |
Thread Index