postgresql/contrib/pgrowlocks/pgrowlocks--1.0.sql

/* contrib/pgrowlocks/pgrowlocks--1.0.sql */

-- complain if script is sourced in psql, rather than via CREATE EXTENSION
\echo Use "CREATE EXTENSION pgrowlocks" to load this file. \quit

CREATE FUNCTION pgrowlocks(IN relname text,
    OUT locked_row TID,		-- row TID
    OUT lock_type TEXT,		-- lock type
    OUT locker XID,		-- locking XID
    OUT multi bool,		-- multi XID?
    OUT xids xid[],		-- multi XIDs
    OUT pids INTEGER[])		-- locker's process id
RETURNS SETOF record
AS 'MODULE_PATHNAME', 'pgrowlocks'
LANGUAGE C STRICT;
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/pgrowlocks/pgrowlocks--1.0.sql */`
Add new contrib function pgrowlocks. See README.pgrowlocks for more details. 2006-04-23 09:12:58 +08:00
Throw a useful error message if an extension script file is fed to psql. 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. 2011-10-13 03:45:03 +08:00			`-- complain if script is sourced in psql, rather than via CREATE EXTENSION`
			`\echo Use "CREATE EXTENSION pgrowlocks" to load this file. \quit`

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 pgrowlocks(IN relname text,`
Restrict pgrowlocks function 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-27 08:13:51 +08:00			`OUT locked_row TID, -- row TID`
			`OUT lock_type TEXT, -- lock type`
			`OUT locker XID, -- locking XID`
			`OUT multi bool, -- multi XID?`
			`OUT xids xid[], -- multi XIDs`
			`OUT pids INTEGER[]) -- locker's process id`
			`RETURNS SETOF record`
Add new contrib function pgrowlocks. See README.pgrowlocks for more details. 2006-04-23 09:12:58 +08:00			`AS 'MODULE_PATHNAME', 'pgrowlocks'`
Restrict pgrowlocks function 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-27 08:13:51 +08:00			`LANGUAGE C STRICT;`