-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


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

>> Well, if you test it as a superuser, it's going to return TRUE every
>> time.

Exactly. So I'm not seeing how we can use USAGE as a reliable test for
the case where a temporary table was created by the same user, but in
another session.

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

iD8DBQFE/LsJvJuQZxSWSsgRAt5mAKDWAWmnljELeRJn+LvdAnpfkwhDIwCfSls8
hR0xST8C88uA4xXrEP6pAh0=
=bHRd
-----END PGP SIGNATURE-----

In response to

• Re: [COMMITTERS] pgsql: Sequences were not being shown due to the use of lowercase `s` at 2006-09-04 22:46:36 from Tom Lane

Responses

• Re: [COMMITTERS] pgsql: Sequences were not being shown due to the use of lowercase `s` at 2006-09-05 00:02:44 from Tom Lane

pgsql-hackers by date

Next:	From: Joshua D. Drake	Date: 2006-09-04 23:51:31
	Subject: Re: [PATCHES] Trivial patch to double vacuum speed
Previous:	From: Tom Lane	Date: 2006-09-04 23:40:54
	Subject: Re: [PATCHES] Trivial patch to double vacuum speed

pgsql-committers by date

Next:	From: Tom Lane	Date: 2006-09-05 00:02:44
	Subject: Re: [COMMITTERS] pgsql: Sequences were not being shown due to the use of lowercase `s`
Previous:	From: Tom Lane	Date: 2006-09-04 23:13:01
	Subject: pgsql: Fix information_schema.key_column_usage to show correct value of