Hi All,
I have found a short term workaround for this. You recreate the index with an added second column with high-cardinality.
ex. CREATE INDEX ON test_indexes USING BTREE (low_cardinality_column, primary_key_id);
We have around 1,500 tables with low-cardinality indexes, so its not the best workaround but one that restores the performance bump for PG11.
Can anyone please shed some light as to why this works?
The only thing I could think of is a locking issue with the leaf nodes.
How much testing is required for this to be considered a proper bug?
Cheers,
Paolo
PLEASE CONSIDER THE ENVIRONMENT BEFORE PRINTING THIS EMAIL
VERIZON CONNECT CONFIDENTIALITY NOTICE
This message is intended for the addressee only and may contain confidential and/or privileged material. Any review, re-transmission, dissemination, reliance upon or other use of this information by persons or entities other than the addressee is prohibited. If you receive this in error, please contact the sender and delete this message. Thank you.
