mirror of
https://git.postgresql.org/git/postgresql.git
synced 2024-12-21 08:29:39 +08:00
029fac2264
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.
23 lines
725 B
PL/PgSQL
23 lines
725 B
PL/PgSQL
/* contrib/pg_freespacemap/pg_freespacemap--1.0.sql */
|
|
|
|
-- Register the C function.
|
|
CREATE FUNCTION pg_freespace(regclass, bigint)
|
|
RETURNS int2
|
|
AS 'MODULE_PATHNAME', 'pg_freespace'
|
|
LANGUAGE C STRICT;
|
|
|
|
-- pg_freespace shows the recorded space avail at each block in a relation
|
|
CREATE FUNCTION
|
|
pg_freespace(rel regclass, blkno OUT bigint, avail OUT int2)
|
|
RETURNS SETOF RECORD
|
|
AS $$
|
|
SELECT blkno, pg_freespace($1, blkno) AS avail
|
|
FROM generate_series(0, pg_relation_size($1) / current_setting('block_size')::bigint - 1) AS blkno;
|
|
$$
|
|
LANGUAGE SQL;
|
|
|
|
|
|
-- Don't want these to be available to public.
|
|
REVOKE ALL ON FUNCTION pg_freespace(regclass, bigint) FROM PUBLIC;
|
|
REVOKE ALL ON FUNCTION pg_freespace(regclass) FROM PUBLIC;
|