| From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Tender Wang <tndrwang(at)gmail(dot)com>, exclusion(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #18500: Detaching a partition with an index manually attached to the parent's index triggers Assert |
| Date: | 2024-06-29 17:56:44 |
| Message-ID: | 202406291756.2d3bmapza7z5@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 2024-Jun-29, Laurenz Albe wrote:
> My example that triggered this assert runs just fine on v16.
Well, in a build without assertions enabled then yes it doesn't crash.
But if you do have asserts enabled in 16, it does crash.
> So while an error is clearly better than a crash, that would constitute
> a regression. Is that really unavoidable? It would be very unfortunate
> if the only way to detach a partition would be to drop some indexes first...
The error would not occur on detach, but on attach, and it'd be intended
to prevent an inconsistent situation. I'm proposing that on older
branches we do what Tender proposed elsewhere, namely to cope with the
detach without crashing (and without leaving inconsistent catalog state,
such as bogus coninhcount values).
--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
"Pero la cosa no es muy grave ..." (le petit Nicolas -- René Goscinny)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Laurenz Albe | 2024-06-29 19:10:33 | Re: BUG #18500: Detaching a partition with an index manually attached to the parent's index triggers Assert |
| Previous Message | Laurenz Albe | 2024-06-29 04:37:12 | Re: BUG #18500: Detaching a partition with an index manually attached to the parent's index triggers Assert |