Re: REPACK (CONCURRENTLY) fails with wrong error for materialized views

Hi Bharath,

Ignore my previous reply. Looks like an issue with the gmail client.

Adding a test should be quick and I can help re-validate as a second eye,
but I would let committer to take a call on this based followed practices.
Otherwise the change is good.

Thanks,
Kiran Kaki.

On Mon, Aug 31, 2026, 1:21 PM Kiran Kaki <itskkpg(at)gmail(dot)com> wrote:

> @Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> look like you
> intended to share something, but email body just says hi.
>
> On Mon, Aug 31, 2026, 9:11 AM Bharath Rupireddy <
> bharath(dot)rupireddyforpostgres(at)gmail(dot)com> wrote:
>
>> Hi,
>>
>> On Sat, Aug 29, 2026 at 1:42 PM Kiran Kaki <itskkpg(at)gmail(dot)com> wrote:
>> >
>> > Hi Bharath,
>> >
>> > I verified the change, and it works as intended. The new check is
>> appropriately placed before replica identity validation. The error is much
>> clearer than the previous "has no identity index" message, and the
>> documentation update looks good to me.
>> >
>> > My only suggestion is to add an automated test as it can help catch
>> any future regressions in this behavior.
>>
>> Thanks for reviewing and verifying the change. I think we can skip the
>> test for this one since the change is straightforward and unlikely to
>> regress.
>>
>> --
>> Bharath Rupireddy
>> Amazon Web Services: https://aws.amazon.com
>>
>