Re: BUG #15609: synchronous_commit=off insert performance regression with secondary indexes

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: "Saul, Jean Paolo" <paolo(dot)saul(at)verizonconnect(dot)com>
Cc: Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #15609: synchronous_commit=off insert performance regression with secondary indexes
Date: 2019-01-30 21:30:07
Message-ID: CAH2-Wzm+6hJutWBMpcHELgedttht9swMsFo5n4fpmojM7iM7ow@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, Jan 29, 2019 at 11:32 PM Saul, Jean Paolo
<paolo(dot)saul(at)verizonconnect(dot)com> wrote:
> But that seems to imply that there was a change deeper in the code that causes this regression on PG10+.
> IMHO I cannot be the only one that noticed this, since PG10 has been out for a while and secondary indexes are quite common in practice.
> I was wondering if anyone can point me in the right direction on how to further investigate this?

What size is bool_idx, and the other indexes once your benchmarks
finish? How do they compare across versions?

--
Peter Geoghegan

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Michael Paquier 2019-01-31 00:36:13 Re: BUG #15114: logical decoding Segmentation fault
Previous Message Tom Lane 2019-01-30 20:07:38 Re: BUG #15613: Bug in PG Planner for Foreign Data Wrappers