diff options
| author | Michael Paquier <michael@paquier.xyz> | 2022-10-27 09:58:44 +0900 |
|---|---|---|
| committer | Michael Paquier <michael@paquier.xyz> | 2022-10-27 09:58:44 +0900 |
| commit | 1b9cd69c5bdd1a331891f282106125e6f2524991 (patch) | |
| tree | c327b4d9d933b10fb310c3bc49ab00fd81a84c1c /src/common/file_utils.c | |
| parent | c591300a8f54d9711157d9a8866f022a257ec4ee (diff) | |
| download | postgresql-1b9cd69c5bdd1a331891f282106125e6f2524991.tar.gz postgresql-1b9cd69c5bdd1a331891f282106125e6f2524991.zip | |
Add some tests to check the SQL functions of control file
As the recent commit 05d4cbf (reverted after as a448e49) has proved,
there is zero coverage for the four SQL functions that can scan the
control file data:
- pg_control_checkpoint()
- pg_control_init()
- pg_control_recovery()
- pg_control_system()
This commit adds a minimal coverage for these functions, checking that
their execution is able to complete. This would have been enough to
catch the problems introduced in the commit mentioned above. More
checks could be done for each individual fields, but it is unclear
whether this would be better than the other checks in place in the
backend code.
Per discussion with Bharath Rupireddy.
Discussion: https://postgr.es/m/Y1d2FZmQmyAhPSRG@paquier.xyz
Diffstat (limited to 'src/common/file_utils.c')
0 files changed, 0 insertions, 0 deletions