From: | Claudio Freire <klaussfreire(at)gmail(dot)com> |
---|---|
To: | Simon Riggs <simon(dot)riggs(at)2ndquadrant(dot)com> |
Cc: | Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>, Peter Geoghegan <pg(at)bowt(dot)ie>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Faster inserts with mostly-monotonically increasing values |
Date: | 2018-03-06 12:52:16 |
Message-ID: | CAGTBQpY2AF8GbBPBW7Q=cuXjJmb=-ihYw=vtwfft8C9j8c_6yg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Mar 6, 2018 at 9:06 AM, Simon Riggs <simon(dot)riggs(at)2ndquadrant(dot)com> wrote:
>> Simon had raised concerns about DESC indexes and whether we need to do the
>> checks for leftmost page in that case. I haven't yet figured out if DESC
>> indexes are actually stored in the reverse order. I am gonna look at that
>> too.
>
> No, I meant that you were testing whether the value was higher (> 0),
> whereas it should be lower (< 0) on DESC indexes.
Isn't that already handled by _bt_compare?
From | Date | Subject | |
---|---|---|---|
Next Message | Teodor Sigaev | 2018-03-06 12:53:49 | Re: General purpose hashing func in pgbench |
Previous Message | Ildus Kurbangaliev | 2018-03-06 12:48:37 | Re: committing inside cursor loop |