| From: | Ilya Matveychikov <matvejchikov(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: Incorrect accounting (n_tup_ins) of non-inserted rows |
| Date: | 2016-03-18 21:52:36 |
| Message-ID: | CAKh5naZqAL8yVG+8JVCB3DtQiwhq3FafXKpFtb18o-H5gKxzaA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
2016-03-18 16:25 GMT+03:00 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
> No, it's not a bug, and it's not going to be fixed. For many of the
> intended applications of those counts (e.g, determining whether
> autovacuum/autoanalyze is needed), this is the correct behavior
> and ignoring actions of failed transactions would be incorrect.
>
Thank you for clarifying.
> The live/dead tuple counts do attempt to take transaction success
> into account; perhaps looking at those would be more helpful for
> your use-case?
I'll take a look on that counters, thanks.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Gould | 2016-03-18 22:08:18 | Re: BUG #13750: Autovacuum slows down with large numbers of tables. More workers makes it slower. |
| Previous Message | David G. Johnston | 2016-03-18 20:57:48 | Re: BUG #14031: Failed to Write to History File |