diff options
| author | Andrew Dunstan | 2022-11-23 19:41:30 +0000 |
|---|---|---|
| committer | Andrew Dunstan | 2022-11-23 19:43:16 +0000 |
| commit | b7a5ef17cf75c712b0fe5c5a20133a88da897aab (patch) | |
| tree | de657ef4e91a377bb87fd66d994304bab9040470 /src/test/isolation | |
| parent | 7b378237aa805711353075de142021b1d40ff3b0 (diff) | |
Simplify WARNING messages from skipped vacuum/analyze on a table
This will more easily accomodate adding new permissions for vacuum and
analyze.
Nathan Bossart following a suggestion from Kyotaro Horiguchi
Discussion: https://postgr.es/m/20220726.104712.912995710251150228.horikyota.ntt@gmail.com
Diffstat (limited to 'src/test/isolation')
| -rw-r--r-- | src/test/isolation/expected/vacuum-conflict.out | 16 |
1 files changed, 8 insertions, 8 deletions
diff --git a/src/test/isolation/expected/vacuum-conflict.out b/src/test/isolation/expected/vacuum-conflict.out index ffde537305f..77e45506c33 100644 --- a/src/test/isolation/expected/vacuum-conflict.out +++ b/src/test/isolation/expected/vacuum-conflict.out @@ -4,7 +4,7 @@ starting permutation: s1_begin s1_lock s2_auth s2_vacuum s1_commit s2_reset step s1_begin: BEGIN; step s1_lock: LOCK vacuum_tab IN SHARE UPDATE EXCLUSIVE MODE; step s2_auth: SET ROLE regress_vacuum_conflict; -s2: WARNING: skipping "vacuum_tab" --- only table or database owner can vacuum it +s2: WARNING: permission denied to vacuum "vacuum_tab", skipping it step s2_vacuum: VACUUM vacuum_tab; step s1_commit: COMMIT; step s2_reset: RESET ROLE; @@ -12,7 +12,7 @@ step s2_reset: RESET ROLE; starting permutation: s1_begin s2_auth s2_vacuum s1_lock s1_commit s2_reset step s1_begin: BEGIN; step s2_auth: SET ROLE regress_vacuum_conflict; -s2: WARNING: skipping "vacuum_tab" --- only table or database owner can vacuum it +s2: WARNING: permission denied to vacuum "vacuum_tab", skipping it step s2_vacuum: VACUUM vacuum_tab; step s1_lock: LOCK vacuum_tab IN SHARE UPDATE EXCLUSIVE MODE; step s1_commit: COMMIT; @@ -22,14 +22,14 @@ starting permutation: s1_begin s2_auth s1_lock s2_vacuum s1_commit s2_reset step s1_begin: BEGIN; step s2_auth: SET ROLE regress_vacuum_conflict; step s1_lock: LOCK vacuum_tab IN SHARE UPDATE EXCLUSIVE MODE; -s2: WARNING: skipping "vacuum_tab" --- only table or database owner can vacuum it +s2: WARNING: permission denied to vacuum "vacuum_tab", skipping it step s2_vacuum: VACUUM vacuum_tab; step s1_commit: COMMIT; step s2_reset: RESET ROLE; starting permutation: s2_auth s2_vacuum s1_begin s1_lock s1_commit s2_reset step s2_auth: SET ROLE regress_vacuum_conflict; -s2: WARNING: skipping "vacuum_tab" --- only table or database owner can vacuum it +s2: WARNING: permission denied to vacuum "vacuum_tab", skipping it step s2_vacuum: VACUUM vacuum_tab; step s1_begin: BEGIN; step s1_lock: LOCK vacuum_tab IN SHARE UPDATE EXCLUSIVE MODE; @@ -40,7 +40,7 @@ starting permutation: s1_begin s1_lock s2_auth s2_analyze s1_commit s2_reset step s1_begin: BEGIN; step s1_lock: LOCK vacuum_tab IN SHARE UPDATE EXCLUSIVE MODE; step s2_auth: SET ROLE regress_vacuum_conflict; -s2: WARNING: skipping "vacuum_tab" --- only table or database owner can analyze it +s2: WARNING: permission denied to analyze "vacuum_tab", skipping it step s2_analyze: ANALYZE vacuum_tab; step s1_commit: COMMIT; step s2_reset: RESET ROLE; @@ -48,7 +48,7 @@ step s2_reset: RESET ROLE; starting permutation: s1_begin s2_auth s2_analyze s1_lock s1_commit s2_reset step s1_begin: BEGIN; step s2_auth: SET ROLE regress_vacuum_conflict; -s2: WARNING: skipping "vacuum_tab" --- only table or database owner can analyze it +s2: WARNING: permission denied to analyze "vacuum_tab", skipping it step s2_analyze: ANALYZE vacuum_tab; step s1_lock: LOCK vacuum_tab IN SHARE UPDATE EXCLUSIVE MODE; step s1_commit: COMMIT; @@ -58,14 +58,14 @@ starting permutation: s1_begin s2_auth s1_lock s2_analyze s1_commit s2_reset step s1_begin: BEGIN; step s2_auth: SET ROLE regress_vacuum_conflict; step s1_lock: LOCK vacuum_tab IN SHARE UPDATE EXCLUSIVE MODE; -s2: WARNING: skipping "vacuum_tab" --- only table or database owner can analyze it +s2: WARNING: permission denied to analyze "vacuum_tab", skipping it step s2_analyze: ANALYZE vacuum_tab; step s1_commit: COMMIT; step s2_reset: RESET ROLE; starting permutation: s2_auth s2_analyze s1_begin s1_lock s1_commit s2_reset step s2_auth: SET ROLE regress_vacuum_conflict; -s2: WARNING: skipping "vacuum_tab" --- only table or database owner can analyze it +s2: WARNING: permission denied to analyze "vacuum_tab", skipping it step s2_analyze: ANALYZE vacuum_tab; step s1_begin: BEGIN; step s1_lock: LOCK vacuum_tab IN SHARE UPDATE EXCLUSIVE MODE; |