diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2023-06-04 11:22:05 -0400 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2023-06-04 11:22:05 -0400 |
| commit | 751ba1a7c168b28a3cc43032e9a1cc996e004054 (patch) | |
| tree | 2d1a984ce568f099ac64144178b1e89356ec4e71 /src/backend/executor/nodeRecursiveunion.c | |
| parent | 0d6fffb4f0b55357e68e8908acd9cf8dc4e178f2 (diff) | |
| download | postgresql-751ba1a7c168b28a3cc43032e9a1cc996e004054.tar.gz postgresql-751ba1a7c168b28a3cc43032e9a1cc996e004054.zip | |
Fix misuse of pg_log_info() for details/hints.
Two places in pg_dump_sort.c were using pg_log_info() to add
more details to a message printed with pg_log_warning().
This is bad, because at default verbosity level we would
print the warning line but not the details. One should use
pg_log_warning_detail() or pg_log_warning_hint() instead.
Commit 9a374b77f got rid of most such abuses, but unaccountably
missed these.
Noted while studying a bug report from Sami Imseih.
Back-patch to v15 where 9a374b77f came in. (Prior versions
don't have the missing-details misbehavior, for reasons
I didn't bother to track down.)
Discussion: https://postgr.es/m/2C1933AB-C2F8-499B-9D18-4AC1882256A0@amazon.com
Diffstat (limited to 'src/backend/executor/nodeRecursiveunion.c')
0 files changed, 0 insertions, 0 deletions