| From: | Michael Paquier <michael(at)paquier(dot)xyz> |
|---|---|
| To: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Álvaro Herrera <alvherre(at)kurilemu(dot)de> |
| Subject: | Re: Tighten ACL check in repack_is_permitted_for_relation() |
| Date: | 2026-08-14 03:51:33 |
| Message-ID: | an6QxAYaS6cVjTEL@paquier.xyz |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Aug 04, 2026 at 01:13:00AM -0700, Bharath Rupireddy wrote:
> I posted this in the thread but starting a new discussion to get some
> quick thoughts:
> https://www.postgresql.org/message-id/CALj2ACX3pyuRS8%2B%2B6L20cJUMRTf_qbbVp69J1btJ3y6%3D77e5gw%40mail.gmail.com
>
> Please find the attached patch for review.
Alvaro, could you comment please?
Perhaps this is something that should be an open item for v19 due to
the fact that it is new code and it can make a REPACK operation more
disruptive depending on unlocky circumstances and concurrent activity?
If Alvaro thinks differently, that's fine, as REPACK is his feature.
it just seems to me like one possible option on the table.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chao Li | 2026-08-14 04:28:17 | Re: Fix detection of truncated zstd-compressed backups |
| Previous Message | Michael Paquier | 2026-08-14 03:48:14 | Re: Report index currently being vacuumed in pg_stat_progress_vacuum |