| From: | Alexander Korotkov <aekorotkov(at)gmail(dot)com> |
|---|---|
| To: | Dmitry Koval <d(dot)koval(at)postgrespro(dot)ru> |
| Cc: | jian he <jian(dot)universality(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Add SPLIT PARTITION/MERGE PARTITIONS commands |
| Date: | 2025-06-03 09:58:24 |
| Message-ID: | CAPpHfdtyzpCZy+6MG-OTAkX_jU+ZoU6GgpZnaM5nV8rs_OKamw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, May 22, 2025 at 11:57 AM Dmitry Koval <d(dot)koval(at)postgrespro(dot)ru> wrote:
> > superuser can bypass all permission checks.
> > superuser can attach any table to the partitioned table as he wants.
>
> That's right.
> Using SUPERUSER may be a rare situation, but it needs to be processed.
I suggest that owner of new partitions produced by ALTER TABLE ...
SPLIT should be the same as owner of original partition. Even if this
operation is done by superuser. Superuser may explicitly set he owner
if needed. I think we need to explicitly document this.
------
Regards,
Alexander Korotkov
Supabase
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Korotkov | 2025-06-03 10:12:28 | Re: Add SPLIT PARTITION/MERGE PARTITIONS commands |
| Previous Message | Laurenz Albe | 2025-06-03 09:37:37 | Re: pg_upgrade: warn about roles with md5 passwords |