mirror of
https://git.postgresql.org/git/postgresql.git
synced 2024-07-16 01:21:12 +02:00
458857cc9d
We have seen one too many reports of people trying to use 9.1 extension files in the old-fashioned way of sourcing them in psql. Not only does that usually not work (due to failure to substitute for MODULE_PATHNAME and/or @extschema@), but if it did work they'd get a collection of loose objects not an extension. To prevent this, insert an \echo ... \quit line that prints a suitable error message into each extension script file, and teach commands/extension.c to ignore lines starting with \echo. That should not only prevent any adverse consequences of loading a script file the wrong way, but make it crystal clear to users that they need to do it differently now. Tom Lane, following an idea of Andrew Dunstan's. Back-patch into 9.1 ... there is not going to be much value in this if we wait till 9.2.
21 lines
755 B
SQL
21 lines
755 B
SQL
/* contrib/pg_buffercache/pg_buffercache--1.0.sql */
|
|
|
|
-- complain if script is sourced in psql, rather than via CREATE EXTENSION
|
|
\echo Use "CREATE EXTENSION pg_buffercache" to load this file. \quit
|
|
|
|
-- 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;
|