| From: | Álvaro Herrera <alvherre(at)kurilemu(dot)de> |
|---|---|
| To: | Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com> |
| Cc: | Baji Shaik <baji(dot)pgdev(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 21:18:08 |
| Message-ID: | ahiwD29RNfVT4tjQ@alvherre.pgsql |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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).
--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
| Attachment | Content-Type | Size |
|---|---|---|
| 0001-Cover-some-errors-and-corner-conditions-in-repack.c.patch | text/x-diff | 4.0 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Masahiko Sawada | 2026-05-28 21:53:40 | Re: Fix race during concurrent logical decoding activation |
| Previous Message | Jacob Champion | 2026-05-28 20:50:26 | Re: Heads Up: cirrus-ci is shutting down June 1st |