On Fri, 2006-02-03 at 22:29 -0500, Bruce Momjian wrote:
> Based on this, I think we should just implement the TRUNCATE/DROP option
> for the table, and avoid the idea of allowing non-logged operations on a
> table that has any data we want recovered after a crash.
Well the only other option is this:
Implement an UNDO at abort like we do for DDL, which would truncate the
table back down to the starting point. That can be made to work for both
cases.
In addition if the starting point was > 0 then we'd need to perform a
VACUUM style operation to remove any index pointers with tids into the
to-be-truncated blocks. That would then make it work for the
with-indexes and/or with-toast cases.
If starting point == 0 we would just truncate the indexes and toast
stuff too.
Most importantly we'd need to do this at recovery time. That bit will
take a bit of work to make it happen right, but seems doable.
So we cover both cases at once, using one lot of logic. But there is a
fair amount of work there, so I'll need to consider whether its 8.2
material or not.
Best Regards, Simon Riggs
