| From: | Francisco Olarte <folarte(at)peoplecall(dot)com> |
|---|---|
| To: | exclusion(at)gmail(dot)com, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #17106: Renaming system types is possible and it potentially leads to a crash |
| Date: | 2021-07-15 15:26:10 |
| Message-ID: | CA+bJJbyPB-JRJAZtqTv3BbzhSKefGcC2BhAa28qMY6Er11==FA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Thu, Jul 15, 2021 at 9:21 AM PG Bug reporting form
<noreply(at)postgresql(dot)org> wrote:
...
> While dropping system types is prohibited (say, you can't DROP TYPE void),
> renaming is not. So the following commands lead to an inevitable crash.
... example removed.
> (Superuser rights required for this, though.)
Any competent programmer can crash a machine, any competent DBA can
crash a DB, anyone with physical access can unplug a server, or set it
on fire.
Given it is not an easy mistake to make ( "DROP type void" is way more
dangerous, being so simple ), I would consider this anecdotal. I doubt
"survive an hostile DBA" is an objective for postgresql.
Francisco Olarte.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2021-07-15 16:09:45 | Re: BUG #17103: WAL segments are not removed after exceeding max_slot_wal_keep_size |
| Previous Message | David G. Johnston | 2021-07-15 14:44:37 | Re: BUG #17110: [FEATURE REQUEST] Log all plans for a query instead of just showing the most optimal plan |