Re: REPACK (CONCURRENTLY) fails when table owner lacks CONNECT

From: Nathan Bossart <nathandbossart(at)gmail(dot)com>
To: Matheus Alcantara <matheusssilv97(at)gmail(dot)com>
Cc: Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org, alvherre(at)kurilemu(dot)de
Subject: Re: REPACK (CONCURRENTLY) fails when table owner lacks CONNECT
Date: 2026-08-27 19:19:14
Message-ID: apCNsqM7uGJwXUa5@nathan
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

The patch looks reasonable to me.

On Thu, Aug 27, 2026 at 03:55:11PM -0300, Matheus Alcantara wrote:
> Added this new test case on attached.

I'm not sure the new tests are necessary. It seems unlikely that we'll
accidentally remove the flags down the road.

--
nathan

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message surya poondla 2026-08-27 19:23:12 Re: [PATCH] Clarify that ssl_groups is for any key exchange groups
Previous Message Nathan Bossart 2026-08-27 19:16:19 Re: REPACK (CONCURRENTLY) doesn't check the table AM