Re: Including PL/PgSQL by default - Mailing list pgsql-hackers

From Joshua D. Drake
Subject Re: Including PL/PgSQL by default
Date
Msg-id 20080221104327.0e34859a@commandprompt.com
Whole thread Raw
In response to Re: Including PL/PgSQL by default  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: Including PL/PgSQL by default  (Andrew Sullivan <ajs@crankycanuck.ca>)
Re: Including PL/PgSQL by default  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thu, 21 Feb 2008 13:33:44 -0500
Andrew Dunstan <andrew@dunslane.net> 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-----

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Including PL/PgSQL by default
Next
From: "Joshua D. Drake"
Date:
Subject: Re: Including PL/PgSQL by default