Re: [PATCH] Fix errhint messages for REPACK (CONCURRENTLY) restrictions

From: Zhenwei Shang <a934172442(at)gmail(dot)com>
To: Baji Shaik <baji(dot)pgdev(at)gmail(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: [PATCH] Fix errhint messages for REPACK (CONCURRENTLY) restrictions
Date: 2026-05-13 06:32:02
Message-ID: CABv9HUmdTmO_f8Ujz=R25MVaD8t2T_goPmeUZjYW9P-9Rwidrw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Baji Shaik <baji(dot)pgdev(at)gmail(dot)com> 于2026年5月13日周三 07:19写道:

> Hi,
>
> The errhint messages added by commit 28d534e2ae0 for REPACK (CONCURRENTLY)
> restrictions have two issues:
>
> 1. They say "REPACK CONCURRENTLY" without parentheses, inconsistent with
> the actual command syntax and the errmsg text elsewhere in the same
> file.
>
> 2. The TOAST relations hint is missing a trailing period.
>
> The attached patch fixes both issues and also switches to the %s pattern
> so translators handle the template without embedding the SQL command name:
>
> Before:
> HINT: REPACK CONCURRENTLY is not supported for TOAST relations
>
> After:
> HINT: REPACK (CONCURRENTLY) is not supported for TOAST relations.
>
> Thanks,
> Baji Shaik
> AWS RDS
>

LGTM. This makes the hint messages consistent with the corresponding error
messages.

Regards,
Zhenwei Shang

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Ashutosh Bapat 2026-05-13 06:45:51 Re: [PATCH] Postpone PROPERTY GRAPH creation in pg_dump to POST-DATA when it depends on a unique constraint
Previous Message Michael Paquier 2026-05-13 06:22:29 Re: Fix unsafe PlannedStmt access in pg_stat_statements