Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1x79A4-0000000088D-224z for pgsql-docs@arkaria.postgresql.org; Thu, 17 Sep 2026 10:16:13 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.98.2) (envelope-from ) id 1x79A3-00000003efB-1OCB for pgsql-docs@arkaria.postgresql.org; Thu, 17 Sep 2026 10:16:11 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1x6zoK-000000013V3-0bss for pgsql-docs@lists.postgresql.org; Thu, 17 Sep 2026 00:17:08 +0000 Received: from mahout.postgresql.org ([2001:4800:3e1:1::227]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1x6zoH-000000002Bk-3WJk for pgsql-docs@lists.postgresql.org; Thu, 17 Sep 2026 00:17:07 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=postgresql.org; s=20171124; h=Message-ID:Date:Reply-To:Cc:From:To:Subject: Content-Transfer-Encoding:MIME-Version:Content-Type:Sender:Content-ID: Content-Description:In-Reply-To:References; bh=DL5BhnxeXAy2rQqaOcHl4aoHT3tXU5lJfwOGvUnm6VI=; b=C3DzYAWHq+aY8rUqz1KpsaOzvs dGylEc13qD5W4ZcgAbu5STjHnNgIZEgD8pyH6Yqfc7fA0tC4Wq3J1+eh9mTfbVSXB9peG66bjRUer 0YsJ2xRiEAgkPnndixmdTeW0XaqrVZyS1XUrMHqJbQsw6I5Imm7/wX2zewXt1g8xNfSCtRaCwUHOJ zxD8Rn6clzI+QOzEbY9XxzN/GGlxn8PKNvLyCNqPBWxHhH8jky/RgvUuMLO3/m5CXcM/myMDkyWy6 1qUZdtY44LtcKQNNYj3Xpnh3oe+Jh25DPrqVxAErgxJ4KNiHnpsee5DSOqKnffKPl01HvyM4taK4G lZgKPrnQ==; Received: from wrigleys.postgresql.org ([2a02:16a8:dc51::60]) by mahout.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1x6zoH-001IK4-1G for pgsql-docs@lists.postgresql.org; Thu, 17 Sep 2026 00:17:05 +0000 Received: from localhost ([127.0.0.1] helo=wrigleys.postgresql.org) by wrigleys.postgresql.org with esmtp (Exim 4.98.2) (envelope-from ) id 1x6zoF-00000005c2o-2lWs for pgsql-docs@lists.postgresql.org; Thu, 17 Sep 2026 00:17:03 +0000 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Subject: DROP DATABASE can be done by superuser To: pgsql-docs@lists.postgresql.org From: PG Doc comments form Cc: kdg@certek.com Reply-To: kdg@certek.com, pgsql-docs@lists.postgresql.org Date: Thu, 17 Sep 2026 00:16:29 +0000 Message-ID: <178960418910.1257.9648976692874205658@wrigleys.postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk The following documentation comment has been logged on the website: Page: https://www.postgresql.org/docs/18/sql-dropdatabase.html Description: The DROP DATABASE article would be a bit clearer and more accurate if after "It can only be executed by the database owner," it said "or a superuser". It does say that in 22.5, "Destroying a Database".