| From: | Baji Shaik <baji(dot)pgdev(at)gmail(dot)com> |
|---|---|
| To: | Álvaro Herrera <alvherre(at)kurilemu(dot)de> |
| Cc: | Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: [PATCH] Improve REPACK (CONCURRENTLY) error messages for unsupported configurations |
| Date: | 2026-05-28 22:08:04 |
| Message-ID: | CA+fm-RNjERQFDA4OsRNiL7sqkZXbrop0dV6Gxu=1qiH=doQScQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, May 28, 2026 at 4:18 PM Álvaro Herrera <alvherre(at)kurilemu(dot)de> wrote:
> While looking these patches over I noticed that we still have some error
> reports cases uncovered. Here's a quick attempt to try and complete
> that.
>
> After this patch I see only one uncovered error path, the one that
> prevents repacking a temp table of another session. That would require
> an isolation test. Not sure it's worth the trouble ... (There's a
> bunch of uncovered "elog(ERROR)" cases, but those are mostly just
> can't-happen conditions, as I understand).
>
LGTM, thanks for adding these.
FWIW I see a couple more uncovered ereport(ERROR) paths 1/ invalid
index (line 813) 2/ shared catalog with USING INDEX (line 580,
needs allow_system_table_mods). But both need unusual setup, so
fine to leave them along with the temp table one.
Thanks,
Baji Shaik.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zsolt Parragi | 2026-05-28 22:08:37 | Re: [PATCH] Add NESTED_STATEMENTS option to EXPLAIN |
| Previous Message | Masahiko Sawada | 2026-05-28 21:53:40 | Re: Fix race during concurrent logical decoding activation |