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-02-03 23:09:49
Message-ID: CAH2-Wznx7S75JMGEA1NWO0YAquX+_Lj7zVpC51HhrxQikAki4Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Sun, Feb 3, 2019 at 2:45 PM Saul, Jean Paolo
<paolo(dot)saul(at)verizonconnect(dot)com> wrote:
> The last post was too long. I think I have a much more simpler example that is easier to replicate.

This new example is very similar to examples that I have personally
come up with. I have no difficulty explaining why the case with lots
of duplicates is slower, so it doesn't really help.

I cannot account for why you can observe a difference across Postgres
versions, though -- that's what I'm having difficulty with. Are you
sure about that effect? There haven't been any directly relevant
changes in this area in many years.

--
Peter Geoghegan

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Robins Tharakan 2019-02-03 23:22:43 DROP TABLE CASCADE doesn't drop dependencies
Previous Message Saul, Jean Paolo 2019-02-03 22:45:12 Re: BUG #15609: synchronous_commit=off insert performance regression with secondary indexes