Re: BUG #19103: Canceled INSERT statement can still influence the performance of subsequent SELECT statement - Mailing list pgsql-bugs

From Álvaro Herrera
Subject Re: BUG #19103: Canceled INSERT statement can still influence the performance of subsequent SELECT statement
Date
Msg-id 202511071550.ldw6ikbkcn4k@alvherre.pgsql
Whole thread Raw
In response to Re: BUG #19103: Canceled INSERT statement can still influence the performance of subsequent SELECT statement  (Tom Lane <tgl@sss.pgh.pa.us>)
List 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)



pgsql-bugs by date:

Previous
From: Amit Langote
Date:
Subject: Re: BUG #19099: Conditional DELETE from partitioned table with non-updatable partition raises internal error
Next
From: Amit Langote
Date:
Subject: Re: BUG #19099: Conditional DELETE from partitioned table with non-updatable partition raises internal error