| From: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
|---|---|
| To: | Zsolt Parragi <zsolt(dot)parragi(at)percona(dot)com> |
| Cc: | shihao zhong <zhong950419(at)gmail(dot)com>, Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Antonin Houska <ah(at)cybertec(dot)at> |
| Subject: | Re: REPACK: warn about skipping foreign partitions |
| Date: | 2026-10-10 17:02:14 |
| Message-ID: | CAHGQGwGonjzb6ffY8jFEHE+HkE3RSDGwukA7zU+L-98xR2J59w@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Oct 10, 2026 at 12:57 AM Zsolt Parragi
<zsolt(dot)parragi(at)percona(dot)com> wrote:
>
> v3 is a trivial rebase to resolve a documentation conflict
In v3, CLUSTER/REPACK warn about foreign partitions during partition
collection, without locking them or checking privileges. OTOH,
VACUUM/VACUUM FULL warn only after locking each partition and
checking privileges.
So, for example, if the user lacks privileges on a foreign partition,
VACUUM/VACUUM FULL report a permission warning, whereas CLUSTER/REPACK
report that foreign tables cannot be processed.
Are these differences intentional, or should CLUSTER/REPACK perform the
checks in the same order as VACUUM/VACUUM FULL?
Regards,
--
Fujii Masao
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Haibo Yan | 2026-10-10 17:03:48 | Re: [PATCH] Fix grouping-set nulling of variable-free grouping expressions |
| Previous Message | David E. Wheeler | 2026-10-10 16:51:48 | Policy for Abandoned Extensions |