From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Postgres Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Must be owner to truncate? |
Date: | 2005-07-08 13:07:41 |
Message-ID: | 20050708130741.GP24207@ns.snowman.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
* Christopher Kings-Lynne (chriskl(at)familyhealth(dot)com(dot)au) wrote:
> >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.
Does truncate not being MVCC-safe cause problems in your situation? It
certainly doesn't in mine and I expect the same is true for alot of
others in the same situation.
Thanks,
Stephen
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2005-07-08 13:29:50 | Re: Must be owner to truncate? |
Previous Message | Stephen Frost | 2005-07-08 13:06:53 | Re: Must be owner to truncate? |