From: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
---|---|
To: | Michael Paquier <michael(at)paquier(dot)xyz>, Andres Freund <andres(at)anarazel(dot)de> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: ALTER TABLE on system catalogs |
Date: | 2018-07-13 09:05:10 |
Message-ID: | 920b7cde-6926-4ad3-936b-7637f0a8188f@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 28.06.18 10:14, Peter Eisentraut wrote:
> On 6/28/18 01:10, Michael Paquier wrote:
>> On Wed, Jun 27, 2018 at 01:37:33PM -0700, Andres Freund wrote:
>>> On 2018-06-27 22:31:30 +0200, Peter Eisentraut wrote:
>>>> I propose that we instead silently ignore attempts to add TOAST tables
>>>> to shared and system catalogs after bootstrapping.
>>>
>>> That seems like an extremely bad idea to me. I'd rather go ahead and
>>> just add the necessary toast tables than silently violate preconditions
>>> that code assumes are fulfilled.
>>
>> Agreed. Joe Conway was working on a patch to do exactly that. I was
>> personally looking for the possibility of having one with pg_authid in
>> v12 :)
>
> OK, that would change things a bit, in that the silent addition of a
> TOAST table would no longer be a problem, but it wouldn't fix the other
> scenarios that end up in an error. If such a patch is forthcoming, we
> can revisit this again afterwards.
After reviewing that thread, I think my patch would still be relevant.
Because the pending proposal is to not add TOAST tables to some catalogs
such as pg_attribute, so my original use case of allowing ALTER TABLE /
SET on system catalogs would still be broken for those tables.
--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Kato, Sho | 2018-07-13 09:08:00 | RE: How to make partitioning scale better for larger numbers of partitions |
Previous Message | Peter Eisentraut | 2018-07-13 08:46:27 | Re: Failed assertion due to procedure created with SECURITY DEFINER option |