postgresql/contrib/pgstattuple/uninstall_pgstattuple.sql

/* $PostgreSQL: pgsql/contrib/pgstattuple/uninstall_pgstattuple.sql,v 1.6 2007/11/13 04:24:28 momjian Exp $ */

-- Adjust this setting to control where the objects get dropped.
SET search_path = public;

DROP FUNCTION pgstattuple(text);
DROP FUNCTION pgstattuple(oid);
DROP FUNCTION pgstatindex(text);
DROP FUNCTION pg_relpages(text);
Add CVS version labels to all install/uninstall scripts. 2007-11-12 23:24:29 -05:00			`/* $PostgreSQL: pgsql/contrib/pgstattuple/uninstall_pgstattuple.sql,v 1.6 2007/11/13 04:24:28 momjian Exp $ */`

Make /contrib install/uninstall script consistent: remove transactions use create or replace function make formatting consistent set search patch on first line Add documentation on modifying *.sql to set the search patch, and mention that major upgrades should still run the installation scripts. Some of these issues were spotted by Tom today. 2007-11-10 22:25:35 -05:00			`-- Adjust this setting to control where the objects get dropped.`
contrib uninstall scripts by David Fetter 2006-02-27 07:54:39 -05:00			`SET search_path = public;`

			`DROP FUNCTION pgstattuple(text);`
Restrict pgstattuple functions to superusers. (This might be too strict, but no permissions check at all is certainly no good.) Clean up usage of some deprecated APIs. 2007-08-26 19:59:50 -04:00			`DROP FUNCTION pgstattuple(oid);`
Clean up some leftover problems in pgstattuple: remove unwanted and unportable elog(NOTICE) report, fix install/uninstall sequence. Itagaki Takahiro 2006-09-03 22:03:04 -04:00			`DROP FUNCTION pgstatindex(text);`
			`DROP FUNCTION pg_relpages(text);`