Re: [COMMITTERS] pgsql: Sequences were not being shown due to the use of lowercase `s` - Mailing list pgsql-hackers

From Greg Sabino Mullane
Subject Re: [COMMITTERS] pgsql: Sequences were not being shown due to the use of lowercase `s`
Date
Msg-id 66ff0cbe1bf948aed11d09e77cc7d62e@biglumber.com
Whole thread Raw
In response to Re: [COMMITTERS] pgsql: Sequences were not being shown due to the use of lowercase 's'  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [COMMITTERS] pgsql: Sequences were not being shown due to the use of lowercase `s`  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


I wrote:
> Sequences were not being shown due to the use of lowercase 's' instead
> of 'S', and the views were not checking for table visibility with
> regards to temporary tables and sequences.

Tom Lane replied:
>> What became of my objection that the test should be on USAGE privilege
>> for the containing schema instead?

I took a stab at implementing this, but what exactly would we check? Looks
like all the temp tables have automatic usage for the same user, according to

SELECT *,has_schema_privilege(oid,'USAGE') FROM pg_namespace;

So I'd need another way to test that the schema was created by another process.
I agree that is_visible may not be ideal for most cases, but it should be okay
if we are simply using it to filter temporary schemas, right?

- --
Greg Sabino Mullane greg@turnstep.com
End Point Corporation
PGP Key: 0x14964AC8 200609041803
http://biglumber.com/x/web?pk=2529DF6AB8F79407E94445B4BC9B906714964AC8
-----BEGIN PGP SIGNATURE-----

iD8DBQFE/Km6vJuQZxSWSsgRAgkaAKC/Nzc8xIcxRC1TW2UJCB76LurWmgCg+Dkk
4HbMsy4H1uwRAUz9lqCSdXg=
=eBg2
-----END PGP SIGNATURE-----



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: [COMMITTERS] pgsql: sslinfo contrib module - information about current SSL
Next
From: Tom Lane
Date:
Subject: Re: [COMMITTERS] pgsql: sslinfo contrib module - information about current SSL