postgresql/contrib/pg_buffercache/pg_buffercache--1.0.sql

/* contrib/pg_buffercache/pg_buffercache--1.0.sql */

-- Register the function.
CREATE FUNCTION pg_buffercache_pages()
RETURNS SETOF RECORD
AS 'MODULE_PATHNAME', 'pg_buffercache_pages'
LANGUAGE C;

-- Create a view for convenient access.
CREATE VIEW pg_buffercache AS
	SELECT P.* FROM pg_buffercache_pages() AS P
	(bufferid integer, relfilenode oid, reltablespace oid, reldatabase oid,
	 relforknumber int2, relblocknumber int8, isdirty bool, usagecount int2);

-- Don't want these to be available to public.
REVOKE ALL ON FUNCTION pg_buffercache_pages() FROM PUBLIC;
REVOKE ALL ON pg_buffercache FROM PUBLIC;
Convert contrib modules to use the extension facility. This isn't fully tested as yet, in particular I'm not sure that the "foo--unpackaged--1.0.sql" scripts are OK. But it's time to get some buildfarm cycles on it. sepgsql is not converted to an extension, mainly because it seems to require a very nonstandard installation process. Dimitri Fontaine and Tom Lane 2011-02-14 09:06:41 +08:00			`/* contrib/pg_buffercache/pg_buffercache--1.0.sql */`
Add pg_buffercache contrib module, from Mark Kirkwood. 2005-03-12 23:36:24 +08:00
			`-- Register the function.`
Avoid use of CREATE OR REPLACE FUNCTION in extension installation files. It was never terribly consistent to use OR REPLACE (because of the lack of comparable functionality for data types, operators, etc), and experimentation shows that it's now positively pernicious in the extension world. We really want a failure to occur if there are any conflicts, else it's unclear what the extension-ownership state of the conflicted object ought to be. Most of the time, CREATE EXTENSION will fail anyway because of conflicts on other object types, but an extension defining only functions can succeed, with bad results. 2011-02-14 10:24:14 +08:00			`CREATE FUNCTION pg_buffercache_pages()`
Add pg_buffercache contrib module, from Mark Kirkwood. 2005-03-12 23:36:24 +08:00			`RETURNS SETOF RECORD`
			`AS 'MODULE_PATHNAME', 'pg_buffercache_pages'`
Clean up CREATE FUNCTION syntax usage in contrib and elsewhere, in particular get rid of single quotes around language names and old WITH () construct. 2006-02-28 00:09:50 +08:00			`LANGUAGE C;`
Add pg_buffercache contrib module, from Mark Kirkwood. 2005-03-12 23:36:24 +08:00
			`-- Create a view for convenient access.`
			`CREATE VIEW pg_buffercache AS`
			`SELECT P.* FROM pg_buffercache_pages() AS P`
Remove useless whitespace at end of lines 2010-11-24 04:27:50 +08:00			`(bufferid integer, relfilenode oid, reltablespace oid, reldatabase oid,`
pg_buffercache needs to be taught about relation forks, as Greg Stark pointed out. 2008-08-14 20:56:41 +08:00			`relforknumber int2, relblocknumber int8, isdirty bool, usagecount int2);`
Remove useless whitespace at end of lines 2010-11-24 04:27:50 +08:00
Convert contrib modules to use the extension facility. This isn't fully tested as yet, in particular I'm not sure that the "foo--unpackaged--1.0.sql" scripts are OK. But it's time to get some buildfarm cycles on it. sepgsql is not converted to an extension, mainly because it seems to require a very nonstandard installation process. Dimitri Fontaine and Tom Lane 2011-02-14 09:06:41 +08:00			`-- Don't want these to be available to public.`
Add pg_buffercache contrib module, from Mark Kirkwood. 2005-03-12 23:36:24 +08:00			`REVOKE ALL ON FUNCTION pg_buffercache_pages() FROM PUBLIC;`
			`REVOKE ALL ON pg_buffercache FROM PUBLIC;`