farrokhi/pg_repack
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Add test for --dry-run

Browse Source 
This should probably be rewritten to actually check OID on old/new tables so
that we don't accidentally execute repack during a dry run.
This commit is contained in:
Steeve Lennmark 2014-01-30 12:53:48 +00:00
parent 5affda20ea
commit d16bdc20d2
2 changed files with 11 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
regress/expected/repack.out
View File

@ -352,3 +352,9 @@ CREATE TABLE trg4 (id integer PRIMARY KEY);
CREATE TRIGGER zzzzzz AFTER UPDATE ON trg4 FOR EACH ROW EXECUTE PROCEDURE trgtest(); CREATE TRIGGER zzzzzz AFTER UPDATE ON trg4 FOR EACH ROW EXECUTE PROCEDURE trgtest();
\! pg_repack --dbname=contrib_regression --table=trg4 \! pg_repack --dbname=contrib_regression --table=trg4
INFO: repacking table "trg4" INFO: repacking table "trg4"
--
-- Dry run
--
\! pg_repack --dbname=contrib_regression --table=tbl_cluster --dry-run
INFO: Dry run enabled, not executing repack
INFO: repacking table "tbl_cluster"

5
regress/sql/repack.sql
View File

@ -206,3 +206,8 @@ CREATE TRIGGER z_repack_trigges BEFORE UPDATE ON trg3 FOR EACH ROW EXECUTE PROCE
CREATE TABLE trg4 (id integer PRIMARY KEY); CREATE TABLE trg4 (id integer PRIMARY KEY);
CREATE TRIGGER zzzzzz AFTER UPDATE ON trg4 FOR EACH ROW EXECUTE PROCEDURE trgtest(); CREATE TRIGGER zzzzzz AFTER UPDATE ON trg4 FOR EACH ROW EXECUTE PROCEDURE trgtest();
\! pg_repack --dbname=contrib_regression --table=trg4 \! pg_repack --dbname=contrib_regression --table=trg4
--
-- Dry run
--
\! pg_repack --dbname=contrib_regression --table=tbl_cluster --dry-run