Re: Must be owner to truncate?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Stephen Frost <sfrost(at)snowman(dot)net>
Cc: andrew(at)supernews(dot)com, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Must be owner to truncate?
Date: 2005-07-08 03:18:51
Message-ID: 7286.1120792731@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Stephen Frost <sfrost(at)snowman(dot)net> writes:
> * Andrew - Supernews (andrew+nonews(at)supernews(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2005-07-08 03:21:42 Re: temp_buffers
Previous Message Tom Lane 2005-07-08 03:03:40 Re: A couple of p.tches for PostgreSQL 64bit support