mirror of
https://github.com/postgres/postgres.git
synced 2025-04-24 10:47:04 +03:00
This provides a newer version of adminpack which works with the newly added default roles to support GRANT'ing to non-superusers access to read and write files, along with related functions (unlinking files, getting file length, renaming/removing files, scanning the log file directory) which are supported through adminpack. Note that new versions of the functions are required because an environment might have an updated version of the library but still have the old adminpack 1.0 catalog definitions (where EXECUTE is GRANT'd to PUBLIC for the functions). This patch also removes the long-deprecated alternative names for functions that adminpack used to include and which are now included in the backend, in adminpack v1.1. Applications using the deprecated names should be updated to use the backend functions instead. Existing installations which continue to use adminpack v1.0 should continue to function until/unless adminpack is upgraded. Reviewed-By: Michael Paquier Discussion: https://postgr.es/m/20171231191939.GR2416%40tamriel.snowman.net
71 lines
2.1 KiB
SQL
71 lines
2.1 KiB
SQL
CREATE EXTENSION adminpack;
|
|
|
|
-- create new file
|
|
SELECT pg_file_write('test_file1', 'test1', false);
|
|
SELECT pg_read_file('test_file1');
|
|
|
|
-- append
|
|
SELECT pg_file_write('test_file1', 'test1', true);
|
|
SELECT pg_read_file('test_file1');
|
|
|
|
-- error, already exists
|
|
SELECT pg_file_write('test_file1', 'test1', false);
|
|
SELECT pg_read_file('test_file1');
|
|
|
|
-- disallowed file paths for non-superusers and users who are
|
|
-- not members of pg_write_server_files
|
|
CREATE ROLE regress_user1;
|
|
|
|
GRANT pg_read_all_settings TO regress_user1;
|
|
GRANT EXECUTE ON FUNCTION pg_file_write(text,text,bool) TO regress_user1;
|
|
|
|
SET ROLE regress_user1;
|
|
SELECT pg_file_write('../test_file0', 'test0', false);
|
|
SELECT pg_file_write('/tmp/test_file0', 'test0', false);
|
|
SELECT pg_file_write(current_setting('data_directory') || '/test_file4', 'test4', false);
|
|
SELECT pg_file_write(current_setting('data_directory') || '/../test_file4', 'test4', false);
|
|
RESET ROLE;
|
|
REVOKE EXECUTE ON FUNCTION pg_file_write(text,text,bool) FROM regress_user1;
|
|
REVOKE pg_read_all_settings FROM regress_user1;
|
|
DROP ROLE regress_user1;
|
|
|
|
-- rename file
|
|
SELECT pg_file_rename('test_file1', 'test_file2');
|
|
SELECT pg_read_file('test_file1'); -- not there
|
|
SELECT pg_read_file('test_file2');
|
|
|
|
-- error
|
|
SELECT pg_file_rename('test_file1', 'test_file2');
|
|
|
|
-- rename file and archive
|
|
SELECT pg_file_write('test_file3', 'test3', false);
|
|
SELECT pg_file_rename('test_file2', 'test_file3', 'test_file3_archive');
|
|
SELECT pg_read_file('test_file2'); -- not there
|
|
SELECT pg_read_file('test_file3');
|
|
SELECT pg_read_file('test_file3_archive');
|
|
|
|
|
|
-- unlink
|
|
SELECT pg_file_unlink('test_file1'); -- does not exist
|
|
SELECT pg_file_unlink('test_file2'); -- does not exist
|
|
SELECT pg_file_unlink('test_file3');
|
|
SELECT pg_file_unlink('test_file3_archive');
|
|
SELECT pg_file_unlink('test_file4');
|
|
|
|
|
|
-- superuser checks
|
|
CREATE USER regress_user1;
|
|
SET ROLE regress_user1;
|
|
|
|
SELECT pg_file_write('test_file0', 'test0', false);
|
|
SELECT pg_file_rename('test_file0', 'test_file0');
|
|
SELECT pg_file_unlink('test_file0');
|
|
SELECT pg_logdir_ls();
|
|
|
|
RESET ROLE;
|
|
DROP USER regress_user1;
|
|
|
|
|
|
-- no further tests for pg_logdir_ls() because it depends on the
|
|
-- server's logging setup
|