Stephan Szabo <sszabo@megazone.bigpanda.com> writes:
> On Sun, 17 Aug 2003, Bruce Momjian wrote:
>> Is this a bug?
> I don't think so. I'd say this is the expected behavior. Part of the
> point is that it fails without checking for matching rows.
To do anything else, you'd have to solve some locking and/or
race-condition problems: rows could be inserted in the other table
while the TRUNCATE runs.
regards, tom lane
