| From: | tgl(at)postgresql(dot)org (Tom Lane) |
|---|---|
| To: | pgsql-committers(at)postgresql(dot)org |
| Subject: | pgsql: Restrict pgstattuple functions to superusers. |
| Date: | 2007-08-28 23:11:13 |
| Message-ID: | 20070828231113.0E07C754201@cvs.postgresql.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers |
Log Message:
-----------
Restrict pgstattuple functions to superusers. While the only one that's
really a glaring security hole is bt_page_items, there's not a very good
use-case for letting ordinary users use 'em, either.
Tags:
----
REL8_2_STABLE
Modified Files:
--------------
pgsql/contrib/pgstattuple:
pgstatindex.c (r1.2.2.2 -> r1.2.2.3)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/pgstattuple/pgstatindex.c?r1=1.2.2.2&r2=1.2.2.3)
pgstattuple.c (r1.25 -> r1.25.2.1)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/contrib/pgstattuple/pgstattuple.c?r1=1.25&r2=1.25.2.1)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2007-08-28 23:17:47 | pgsql: Add a debug logging message when a resource manager rejects an |
| Previous Message | Tom Lane | 2007-08-28 22:59:30 | pgsql: Reduce the permissions check needed to use pgrowlocks() to having |