Re: Truncation of mapped catalogs (whether local or shared) leads to server crash
| От | Tom Lane |
|---|---|
| Тема | Re: Truncation of mapped catalogs (whether local or shared) leads to server crash |
| Дата | |
| Msg-id | 3596911.1718720426@sss.pgh.pa.us обсуждение исходный текст |
| Ответ на | Re: Truncation of mapped catalogs (whether local or shared) leads to server crash (Robert Haas <robertmhaas@gmail.com>) |
| Ответы |
Re: Truncation of mapped catalogs (whether local or shared) leads to server crash
|
| Список | pgsql-hackers |
Robert Haas <robertmhaas@gmail.com> writes:
> On Tue, Jun 18, 2024 at 8:10 AM Ashutosh Sharma <ashu.coek88@gmail.com> wrote:
>> Executing below commands:
>> -- set allow_system_table_mods TO on;
>> -- truncate table pg_type;
> If the operation isn't allowed without turning on
> allow_system_table_mods, that means that doing it is probably a bad
> idea and will probably break stuff, as happened here.
Nothing good can come of truncating *any* core system catalog --- what
do you think you'll still be able to do afterwards?
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.
regards, tom lane
В списке pgsql-hackers по дате отправления: