| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Michael Paquier <michael(at)paquier(dot)xyz> |
| Cc: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Jeremy Finzel <finzelj(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Index corruption / planner issue with one table in my pg 11.6 instance |
| Date: | 2019-12-10 02:56:26 |
| Message-ID: | CAH2-Wzk2XJUqVRqRTBVnaTKCW38FOJu7rJTzC1a6Ud_pFLB_CA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Dec 9, 2019 at 6:33 PM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> Something new as of 11 is that btree indexes can be built in parallel,
> and before releasing it we found some bugs with covering indexes.
> Perhaps we have an issue hidden behind one of these, but hard to be
> sure.
I doubt it.
Jeremy did not report queries that give wrong answers. He only said
that the optimizer refused to use one particular index, before a
VACUUM FULL seemingly corrected the problem. OTOH, Jeremy did report
using contrib/amcheck on the index, which didn't complain. (Note also
that the amcheck functions will throw an error with an !indisvalid
index.)
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2019-12-10 04:22:13 | Re: PATCH: logical_work_mem and logical streaming of large in-progress transactions |
| Previous Message | Thomas Munro | 2019-12-10 02:41:15 | Re: Windows UTF-8, non-ICU collation trouble |