Re: TRUNCATE privilege vs information_schema

From: "Dave Page" <dpage(at)pgadmin(dot)org>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: TRUNCATE privilege vs information_schema
Date: 2008-09-08 07:35:20
Message-ID: 937d27e10809080035y2a75ea65u9be28bf68c9db62a@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Sep 7, 2008 at 9:52 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Whilst going through the pending patch to add TRUNCATE as a separate
> permission, I noticed that it neglected to add TRUNCATE to the various
> columns in information_schema that display privileges. I wonder whether
> we should do so, or whether we should restrict information_schema to
> only show SQL-spec-compatible privileges.

If we add that, how many other places are we likely to creep from the
spec in the future? I think we should keep it as spec-compliant as
possible.

--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Heikki Linnakangas 2008-09-08 07:49:36 Re: [PATCHES] TODO item: Implement Boyer-Moore searching (First time hacker)
Previous Message M2Y 2008-09-08 07:34:56 Re: Some newbie questions