Re: stats for failed transactions (was Re: [GENERAL] VACUUM Question) - Mailing list pgsql-hackers

From Tom Lane
Subject Re: stats for failed transactions (was Re: [GENERAL] VACUUM Question)
Date
Msg-id 11969.1138464816@sss.pgh.pa.us
Whole thread Raw
In response to Re: stats for failed transactions (was Re: [GENERAL] VACUUM  ("Matthew T. O'Connor" <matthew@zeut.net>)
List pgsql-hackers
"Matthew T. O'Connor" <matthew@zeut.net> writes:
> Tom Lane wrote:
>> the only full solution will involve backends doing some extra work at
>> subtransaction commit/abort so that they can report properly classified
>> update counts.

> Any guess as to the performance implications?

Pushing some counts from one place to another doesn't seem that
expensive, but it'd be nice to avoid scanning a lot of unrelated
table-stats entries to find the ones that have to be adjusted.
Not sure what it'll take exactly.

Or we could blow it off for the time being.  Certainly, getting
things right at the top-transaction level would already be a big
leg up in accuracy from where we are, and I don't think that would
be hard at all.
        regards, tom lane


pgsql-hackers by date:

Previous
From: "Matthew T. O'Connor"
Date:
Subject: Re: stats for failed transactions (was Re: [GENERAL] VACUUM
Next
From: Josh Berkus
Date:
Subject: Re: stats for failed transactions (was Re: [GENERAL] VACUUM