Re: BUG #1937: Parts of information_schema only accessible to owner

From: "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>
To: Tony Marston <tony(at)marston-home(dot)demon(dot)co(dot)uk>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #1937: Parts of information_schema only accessible to owner
Date: 2005-10-04 16:45:04
Message-ID: 20051004164504.GN40138@pervasive.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

You might want to use http://pgfoundry.org/projects/newsysviews/
instead. We've also talked about changing our naming to come more
in-line with information schema.

On Tue, Oct 04, 2005 at 01:58:36PM +0100, Tony Marston wrote:
>
> The following bug has been logged online:
>
> Bug reference: 1937
> Logged by: Tony Marston
> Email address: tony(at)marston-home(dot)demon(dot)co(dot)uk
> PostgreSQL version: 8.0.3
> Operating system: Windows XP
> Description: Parts of information_schema only accessible to owner
> Details:
>
> I have been trying to access parts of the information_schema as an ordinary
> user, not as owner, and I am encountering instances where I cannot retrieve
> any rows at all, or where some of the columns are empty when they should not
> be.
>
> This sounds like a faulty implementation to me, with too many restrictions.
> As far as I am concerned if I have access privileges on an object then I
> should be able to see ALL information_schema details regarding that object.
> Being able to view data in the information_schema does not give me the
> ability to do anything that is not already permitted in the privilges
> system, so why is access to such data being blocked?
>
> As an example, in the view "information_schema.columns" I can only see the
> entry in COLUMN_DEFAULT if I am the owner. Why is this? What is the logic
> behind this decision? What possible security breach is blocked by witholding
> this information?
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: explain analyze is your friend
>

--
Jim C. Nasby, Sr. Engineering Consultant jnasby(at)pervasive(dot)com
Pervasive Software http://pervasive.com work: 512-231-6117
vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Jeff MacDonald 2005-10-04 19:29:23 BUG #1938: pg_dump mis-intreprets "default now()";
Previous Message Jim C. Nasby 2005-10-04 16:42:52 Re: BUG #1927: incorrect timestamp returned