Re: DROP TABLESPACE causes panic during recovery

Gavin Sherry <swm@linuxworld.com.au> writes:

> >     CREATE TABLESPACE
> >     ...
> >     much time passes
> >     ...
> >     CHECKPOINT
> >     ...
> >     modify tables in tablespace
> >     drop tables in tablespace
> >     DROP TABLESPACE
> >     ...
> >     system crash

What happens here if no table spaces are involved?

It just creates bogus tables with partial data counting on the restore to see
the drop table command later and delete the corrupt tables?

Does that pose any danger with PITR? The scenario above seems ok since if the
PITR starting point is after the drop table/tablespace then presumably the
recovery target has to be after that as well? Is there any other scenario
where the partial data files could escape the recovery process?

-- 
greg