On Tue, Mar 25, 2025 at 8:52 PM Rafael Thofehrn Castro <rafaelt...@gmail.com> wrote: > This first version of the progressive explain feature was designed to only > keep > track of initial query called by the backend, ignoring all subquery calls. So > I believe we don't need to worry about having to add custom logic in > AbortSubTransaction(). In case query errors out AbortTransaction() will be > called > and everything related to progressive explains will be cleaned.
Suppose: BEGIN; SELECT 1; SAVEPOINT bob; progressively explain something that aborts I think in this case we will call AbortSubTransaction(), not AbortTransaction(). -- Robert Haas EDB: http://www.enterprisedb.com
