Re: Pathological performance when inserting many NULLs into a unique index

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Pathological performance when inserting many NULLs into a unique index
Date: 2019-04-23 17:40:03
Message-ID: CAH2-Wz=ihyzJFo3UFg+QFRC=euP63DdwVrZDiEZCEMj1p7kTQw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Apr 19, 2019 at 6:34 PM Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
> Attached revision does it that way, specifically by adding a new field
> to the insertion scankey struct (BTScanInsertData).

Pushed.

--
Peter Geoghegan

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2019-04-23 18:01:14 Re: finding changed blocks using WAL scanning
Previous Message Andres Freund 2019-04-23 17:39:13 Re: Unhappy about API changes in the no-fsm-for-small-rels patch