-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 21 Feb 2008 13:33:44 -0500 Andrew Dunstan <[EMAIL PROTECTED]> wrote: > > That's not true. The public schema has public UC privs, and always > has had. >
This disproves my point how? > There is nothing surprising (expect possibly to you) here. > It is not a surprise to me, you can check the archives I bring it up often. It is poor implementation and proof that the theoretical security implications that are being brought up in this thread are far from the practical reality. Sincerely, Joshua D. Drake - -- The PostgreSQL Company since 1997: http://www.commandprompt.com/ PostgreSQL Community Conference: http://www.postgresqlconference.org/ Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate PostgreSQL SPI Liaison | SPI Director | PostgreSQL political pundit -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFHvcZRATb/zqfZUUQRAvp9AJ9nLf/CW3NvscqJ7zciZWDVil0X8QCghNZY tiUyxmuWyd4DFjrRZdz2Dao= =IQdD -----END PGP SIGNATURE----- ---------------------------(end of broadcast)--------------------------- TIP 4: Have you searched our list archives? http://archives.postgresql.org
