Re: Tighten ACL check in repack_is_permitted_for_relation()

From: Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
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-17 03:15:00
Message-ID: CALj2ACWT1PN0shzrgmYHVObZ7EPhkfKovVN4B-MyO+Gb2-iS0w@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On Thu, Aug 13, 2026 at 8:51 PM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
>
> 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.

I added this as an open item for PG19 to get some thoughts before the
release. Thanks.

--
Bharath Rupireddy
Amazon Web Services: https://aws.amazon.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Richard Guo 2026-08-17 03:26:59 Fix CPU cost of right-semi and right-anti hash joins
Previous Message Bertrand Drouvot 2026-08-17 03:07:46 Re: basebackup: do not verify checksums on pages written before enabling checksums