| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Jesper Pedersen <jesper(dot)pedersen(at)redhat(dot)com>, Mithun Cy <mithun(dot)cy(at)enterprisedb(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Hash Indexes |
| Date: | 2016-09-14 02:43:15 |
| Message-ID: | CAA4eK1+yY3FCJ+cLvG=EBpR16rZBhypQgnE314nZJQ6C_RVFEA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Sep 13, 2016 at 5:46 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Thu, Sep 8, 2016 at 12:32 AM, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
>> Hmm. I think page or block is a concept of database systems and
>> buckets is a general concept used in hashing technology. I think the
>> difference is that there are primary buckets and overflow buckets. I
>> have checked how they are referred in one of the wiki pages [1],
>> search for overflow on that wiki page. Now, I think we shouldn't be
>> inconsistent in using them. I will change to make it same if I find
>> any inconsistency based on what you or other people think is the
>> better way to refer overflow space.
>
> In the existing source code, the terminology 'overflow page' is
> clearly preferred to 'overflow bucket'.
>
Okay, point taken. Will update it in next version of patch.
--
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Langote | 2016-09-14 02:48:55 | Comment typo in execIndexing.c |
| Previous Message | Tatsuo Ishii | 2016-09-14 02:09:57 | Re: Event trigger and CREATE/ALTER ROLE/USER |