Re: Truncation of mapped catalogs (whether local or shared) leads to server crash - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Truncation of mapped catalogs (whether local or shared) leads to server crash
Date
Msg-id 3601887.1718722516@sss.pgh.pa.us
Whole thread Raw
In response to Re: Truncation of mapped catalogs (whether local or shared) leads to server crash  (Ashutosh Sharma <ashu.coek88@gmail.com>)
Responses Re: Truncation of mapped catalogs (whether local or shared) leads to server crash
List pgsql-hackers
Ashutosh Sharma <ashu.coek88@gmail.com> writes:
> On Tue, Jun 18, 2024 at 7:50 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> I think the assertion you noticed is there because the code path gets
>> traversed during REINDEX, which is an operation we do support on
>> system catalogs.  I have zero interest in making truncate work
>> on them.

> I agree with you on that point. How about considering a complete
> restriction instead?

You already broke the safety seal by enabling allow_system_table_mods.
Perhaps the documentation of that is not scary enough?

        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.  Ill-advised use of this setting can
        cause irretrievable data loss or seriously corrupt the database
        system.

            regards, tom lane



pgsql-hackers by date:

Previous
From: Dave Page
Date:
Subject: Re: Meson far from ready on Windows
Next
From: Andres Freund
Date:
Subject: Re: consider -Wmissing-variable-declarations