Stephen Frost <sfrost@snowman.net> writes:
> * Andrew - Supernews (andrew+nonews@supernews.com) wrote:
>> It's not MVCC-safe even with the AccessExclusive lock;
> This seems like something which should probably be fixed,
You've missed the point entirely: this *cannot* be fixed, at least not
without giving up the performance advantages that make TRUNCATE
interesting.
regards, tom lane