| From: | Kasahara Tatsuhito <kasahara(dot)tatsuhito(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>, Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Tid scan increments value of pg_stat_all_tables.seq_scan. (but not seq_tup_read) |
| Date: | 2020-02-06 06:04:58 |
| Message-ID: | CAP0=ZVJrskNwuG=WUYNX6nQLnzCPk49NLi40O+fmt+Uy13q5_g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On Thu, Feb 6, 2020 at 11:48 AM Andres Freund <andres(at)anarazel(dot)de> wrote:
> I think it'd be good if we could guard against b) via an isolation
> test. It's more painful to do that for a), due to the unreliability of
> stats at the moment (we have some tests, but they take a long time).
Thanks for your advise, and agreed.
I added a new (but minimal) isolation test for the case of tid scan.
(v12 and HEAD will be failed this test. v11 and HEAD with my patch
will be passed)
Best regards,
--
Tatsuhito Kasahara
kasahara.tatsuhito _at_ gmail.com
| Attachment | Content-Type | Size |
|---|---|---|
| fix_tidscan_issues_v2.patch | application/octet-stream | 3.9 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Langote | 2020-02-06 06:11:01 | typo in set_rel_consider_parallel() |
| Previous Message | Andy Fan | 2020-02-06 06:01:27 | Re: [PATCH] Erase the distinctClause if the result is unique by definition |