pgsql: Clean up checking for pg_dumpall output directory

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Clean up checking for pg_dumpall output directory
Date: 2025-04-06 21:05:17
Message-ID: E1u1XB7-0030yJ-1z@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Clean up checking for pg_dumpall output directory

Coverity objected to the original code, and in any case this is much
cleaner, using the existing routine pg_check_dir() instead of rolling
its own test.

Per suggestion from Tom Lane.

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/643a1a61985bef25904965053020057200d4ae48

Modified Files
--------------
src/bin/pg_dump/pg_dumpall.c | 58 +++++++++++++++-----------------------------
1 file changed, 20 insertions(+), 38 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Michael Paquier 2025-04-06 21:29:04 Re: pgsql: pg_upgrade: Fix inconsistency in memory freeing
Previous Message Tom Lane 2025-04-06 20:27:56 pgsql: Doc: fix PDF "contents ... exceed the available area" warnings.