Re: DROP TABLESPACE causes panic during recovery - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: DROP TABLESPACE causes panic during recovery
Date
Msg-id 200408050401.i7541Cn21636@candle.pha.pa.us
Whole thread Raw
In response to Re: DROP TABLESPACE causes panic during recovery  ("Andrew Dunstan" <andrew@dunslane.net>)
Responses Re: DROP TABLESPACE causes panic during recovery  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Andrew Dunstan wrote:
> Tom Lane said:
> >The
> > scenario that causes the problem is
> >
> >     CREATE TABLESPACE
> >     ...
> >     much time passes
> >     ...
> >     CHECKPOINT
> >     ...
> >     modify tables in tablespace
> >     drop tables in tablespace
> >     DROP TABLESPACE
> >     ...
> >     system crash
> >
> > Now the system needs to replay from the last checkpoint.  It's going to
> > hit updates to tables that aren't there anymore in a tablespace that's
> > not there anymore.  There will not be anything in the replayed part of
> > the log that will give a clue where that tablespace was physically.
> >
> 
> Could we create the tables in the default tablespace? Or create a dummy
> tablespace (since it's not there we expect it to be removed anyway, don't
> we?) I guess the big danger would be running out of disk space, but maybe
> that is a lower risk than this one.

Uh, why is the symlink not going to be there already?

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
359-1001+  If your life is a hard drive,     |  13 Roberts Road +  Christ can be your backup.        |  Newtown Square,
Pennsylvania19073
 


pgsql-hackers by date:

Previous
From: Greg Stark
Date:
Subject: Re: DROP TABLESPACE causes panic during recovery
Next
From: Tom Lane
Date:
Subject: Re: DROP TABLESPACE causes panic during recovery