| From: | "Andrew Dunstan" <andrew(at)dunslane(dot)net> |
|---|---|
| To: | <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | <swm(at)linuxworld(dot)com(dot)au>, <kevin(at)sysexperts(dot)com>, <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: DROP TABLESPACE causes panic during recovery |
| Date: | 2004-08-05 03:49:09 |
| Message-ID: | 4400.24.211.141.25.1091677749.squirrel@www.dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2004-08-05 03:51:58 | Re: [BUGS] casting strings to multidimensional arrays yields strange results |
| Previous Message | Christopher Kings-Lynne | 2004-08-05 03:38:55 | Re: DROP TABLESPACE causes panic during recovery |