Re: WIP: Covering + unique indexes.

From: Andrew Borodin <borodin(at)octonica(dot)com>
To: Anastasia Lubennikova <a(dot)lubennikova(at)postgrespro(dot)ru>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Anastasia Lubennikova <lubennikovaav(at)gmail(dot)com>
Subject: Re: WIP: Covering + unique indexes.
Date: 2016-08-17 07:36:53
Message-ID: CAJEAwVEnMQzMw-ZJHU4=yMVAW7Jny2HwXcFZ2US_m1vnGaG2Xg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> That was a bug caused by high key truncation, that occurs when index has more than 3 levels. Fixed.
Affirmative. I've tested index construction with 100M rows and
subsequent execution of select queries using index, works fine.

Best regards, Andrey Borodin, Octonica & Ural Federal University.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Oskari Saarenmaa 2016-08-17 07:58:09 Use pread and pwrite instead of lseek + write and read
Previous Message Jeff Janes 2016-08-17 06:32:00 EXLCUDE constraints and Hash indexes