| From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Gavin Sherry <swm(at)linuxworld(dot)com(dot)au>, Kevin Brown <kevin(at)sysexperts(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: DROP TABLESPACE causes panic during recovery |
| Date: | 2004-08-05 03:38:55 |
| Message-ID: | 4111ABCF.1020701@familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> We do need to do that, but it will *not* solve this problem. 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.
Maybe we need to create a new system tablespace: pg_recovery
Then when this situation occurs, if the tablespace cannot be located, we
recrated the objects in the system 'pg_recovery' tablespace or something.
I dunno :)
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2004-08-05 03:49:09 | Re: DROP TABLESPACE causes panic during recovery |
| Previous Message | Gavin Sherry | 2004-08-05 03:22:26 | Re: DROP TABLESPACE causes panic during recovery |