| From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: allow_system_table_mods stuff |
| Date: | 2019-11-29 09:30:53 |
| Message-ID: | 440e42c8-948d-d489-cf2f-1f266e087942@2ndquadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2019-11-28 17:11, Tom Lane wrote:
> I read through the patch set and have just one quibble: in the
> proposed new docs,
>
> + Allows modification of the structure of system tables as well as
> + certain other risky actions on system tables. This is otherwise not
> + allowed even for superusers. This is used by
> + <command>initdb</command>. Inconsiderate use of this setting can
> + cause irretrievable data loss or seriously corrupt the database
> + system. Only superusers can change this setting.
>
> "Inconsiderate" doesn't seem like le mot juste. Maybe "Ill-advised"?
>
> (I'm also wondering whether the sentence about initdb is worth keeping.)
committed with those adjustments
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fabien COELHO | 2019-11-29 09:34:05 | Re: pgbench - add \aset to store results of a combined query |
| Previous Message | Yugo Nagata | 2019-11-29 09:19:54 | Re: Implementing Incremental View Maintenance |