From 36e08d6d8afb44a704ff228fd4ced2cf2976235b Mon Sep 17 00:00:00 2001 From: Ashesh Vashi Date: Mon, 14 Sep 2026 23:08:27 +0530 Subject: [PATCH] fix(maintenance): drop a duplicated comment block above the database guard The four-line comment explaining why an empty database must be rejected was pasted twice above the guard in create_maintenance_job(). Comment only; no behaviour change. --- web/pgadmin/tools/maintenance/__init__.py | 4 ---- 1 file changed, 4 deletions(-) diff --git a/web/pgadmin/tools/maintenance/__init__.py b/web/pgadmin/tools/maintenance/__init__.py index 4f627e8f9..29d9b192b 100644 --- a/web/pgadmin/tools/maintenance/__init__.py +++ b/web/pgadmin/tools/maintenance/__init__.py @@ -217,10 +217,6 @@ def create_maintenance_job(sid, did): if validation_error is not None: return bad_request(errormsg=validation_error) - # A target database is mandatory. Reject an empty/missing value up front: - # otherwise PGDATABASE is left unset and libpq falls back down its chain to - # a database named after the login role, silently running maintenance on - # the wrong database instead of failing safely. # A target database is mandatory. Reject an empty/missing value up front: # otherwise PGDATABASE is left unset and libpq falls back down its chain to # a database named after the login role, silently running maintenance on