Re: Must be owner to truncate?

From: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Stephen Frost <sfrost(at)snowman(dot)net>, Postgres Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Must be owner to truncate?
Date: 2005-07-08 02:23:07
Message-ID: 42CDE38B.4070300@familyhealth.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> There are other reasons for restricting it:
> * truncate takes a much stronger lock than a plain delete does.
> * truncate is not MVCC-safe.
>
> I don't really agree with the viewpoint that truncate is just a quick
> DELETE, and so I do not agree that DELETE permissions should be enough
> to let you do a TRUNCATE.

Ah. I didn't realise that 2nd point. I don't care so much about the
stronger lock in my application.

Chris

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Christopher Kings-Lynne 2005-07-08 02:26:13 Re: Pg_autovacuum on FreeBSD
Previous Message Christopher Kings-Lynne 2005-07-08 02:21:31 Re: Must be owner to truncate?