| From: | Álvaro Herrera <alvherre(at)kurilemu(dot)de> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, "jinhui(dot)lai(at)qq(dot)com" <jinhui(dot)lai(at)qq(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: BUG #19103: Canceled INSERT statement can still influence the performance of subsequent SELECT statement |
| Date: | 2025-11-07 15:51:54 |
| Message-ID: | 202511071550.ldw6ikbkcn4k@alvherre.pgsql |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 2025-Nov-04, Tom Lane wrote:
> It is not. The reason ROLLBACK is essentially free in Postgres
> is that some of the ensuing cleanup work gets done during
> subsequent table accesses. Some other DBMSes do that differently,
> but that's our choice and we're not likely to revisit it.
At least, it's the choice we have made in heapam. It's possible to make
different choices for other table AMs -- for instance, I bet OrioleDB
has made a different choice here, because of its claim that vacuum is
not needed.
--
Álvaro Herrera Breisgau, Deutschland — https://www.EnterpriseDB.com/
"El hombre nunca sabe de lo que es capaz hasta que lo intenta" (C. Dickens)
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Langote | 2025-11-08 05:19:36 | Re: BUG #19099: Conditional DELETE from partitioned table with non-updatable partition raises internal error |
| Previous Message | Amit Langote | 2025-11-07 09:23:16 | Re: BUG #19099: Conditional DELETE from partitioned table with non-updatable partition raises internal error |