From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
---|---|
To: | Simon Riggs <simon(dot)riggs(at)enterprisedb(dot)com> |
Cc: | Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>, Dilip Kumar <dilipbalaut(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, Sadhuprasad Patro <b(dot)sadhu(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Next Steps with Hash Indexes |
Date: | 2021-10-13 19:23:23 |
Message-ID: | CAH2-WzkHT7Hu0M6u5dgyG3GfuzDca+QBRO=+yVmqfdBeGq-QQA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Oct 13, 2021 at 12:15 PM Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
> Are you sure? I know that nbtree index tuples for a single-column int8
> index are exactly the same size as those from a single column int4
> index, due to alignment overhead at the tuple level. So my guess is
> that hash index tuples (which use the same basic IndexTuple
> representation) work in the same way.
I'm assuming a 64-bit architecture here, by the way. That assumption
shouldn't matter, since of course approximately 100% of all computers
that run Postgres are 64-bit these days.
--
Peter Geoghegan
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2021-10-13 19:49:41 | Re: AW: VS2022: Support Visual Studio 2022 on Windows |
Previous Message | Peter Geoghegan | 2021-10-13 19:15:47 | Re: Next Steps with Hash Indexes |