aboutsummaryrefslogtreecommitdiff
path: root/src/backend/tcop/postgres.c
diff options
context:
space:
mode:
authorMichael Paquier <michael@paquier.xyz>2021-09-17 15:53:01 +0900
committerMichael Paquier <michael@paquier.xyz>2021-09-17 15:53:01 +0900
commitcddcf7842c31b4d07ca75439f6b4ddacaadbbd0d (patch)
tree000af02949f542a4391cc088952dbacfc8774e19 /src/backend/tcop/postgres.c
parent5adb06732d7fac8171609392ea83f18bc8f285f4 (diff)
downloadpostgresql-cddcf7842c31b4d07ca75439f6b4ddacaadbbd0d.tar.gz
postgresql-cddcf7842c31b4d07ca75439f6b4ddacaadbbd0d.zip
Clarify some errors in pg_receivewal when closing WAL segments
A WAL segment closed during a WAL stream for pg_receivewal would generate incorrect error messages depending on the context, as the file name used when referring to a WAL segment ignored partial files or the compression method used. In such cases, the error message generated (failure on close, seek or rename) would not match a physical file name. The same code paths are used by pg_basebackup, but it uses no partial suffix so it is not impacted. 7fbe0c8 has introduced in walmethods.c a callback to get the exact physical file name used for a given context, this commit makes use of it to improve those error messages. This could be extended to more code paths of pg_basebackup/ in the future, if necessary. Extracted from a larger patch by the same author. Author: Georgios Kokolatos Discussion: https://postgr.es/m/ZCm1J5vfyQ2E6dYvXz8si39HQ2gwxSZ3IpYaVgYa3lUwY88SLapx9EEnOf5uEwrddhx2twG7zYKjVeuP5MwZXCNPybtsGouDsAD1o2L_I5E=@pm.me
Diffstat (limited to 'src/backend/tcop/postgres.c')
0 files changed, 0 insertions, 0 deletions