| From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
|---|---|
| To: | "kdg(at)certek(dot)com" <kdg(at)certek(dot)com>, "pgsql-docs(at)lists(dot)postgresql(dot)org" <pgsql-docs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: DROP DATABASE can be done by superuser |
| Date: | 2026-09-17 11:06:49 |
| Message-ID: | CAKFQuwYp39ENMAFnO9ku-xoO417pyL_uJBj_sgnFU7CFbNat4A@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
On Wednesday, September 16, 2026, PG Doc comments form <
noreply(at)postgresql(dot)org> wrote:
> 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".
>
Personally I prefer saving the few characters since everything can be done
by a superuser. In any case, we are already inconsistent in whether we
make that point throughout the SQL Command chapter and I don’t see much
value in only changing this specific one in isolation.
David J.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2026-09-17 19:55:07 | Re: 8.5.1. Date/Time Input |
| Previous Message | PG Doc comments form | 2026-09-17 00:16:29 | DROP DATABASE can be done by superuser |