|From:||Peter Geoghegan <pg(at)bowt(dot)ie>|
|To:||"Saul, Jean Paolo" <paolo(dot)saul(at)verizonconnect(dot)com>|
|Cc:||Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>|
|Subject:||Re: BUG #15609: synchronous_commit=off insert performance regression with secondary indexes|
|Views:||Raw Message | Whole Thread | Download mbox | Resend email|
On Tue, Jan 29, 2019 at 2:05 PM Saul, Jean Paolo
> Before each test run, I drop and recreate the table and indexes.
What happens if you don't create bool_idx, or replace it with another
index on some other column? I notice that you didn't show any case
that doesn't have this index, except for the PK-only case, which is
actually faster. I surmise that that's the common factor in all of the
test cases where you have observed a regression. It would be nice to
confirm or disprove this theory.
The nbtree code is known to deal poorly with low cardinality indexes
, something I'm currently working to address. Are you comparing
installations that are on the same hardware and operating system?
|Next Message||Saul, Jean Paolo||2019-01-30 04:26:49||Re: BUG #15609: synchronous_commit=off insert performance regression with secondary indexes|
|Previous Message||Saul, Jean Paolo||2019-01-30 00:59:20||Re: BUG #15609: synchronous_commit=off insert performance regression with secondary indexes|