| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
|---|---|
| To: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
| Cc: | Simon Riggs <simon(dot)riggs(at)enterprisedb(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Doc chapter for Hash Indexes |
| Date: | 2021-06-22 05:06:57 |
| Message-ID: | CAA4eK1K8tQXSQP6q71WF3UfZvjeBaSquupbgXrUb9OD94NPW3w@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Jun 22, 2021 at 4:25 AM Justin Pryzby <pryzby(at)telsasoft(dot)com> wrote:
>
> On Mon, Jun 21, 2021 at 02:08:12PM +0100, Simon Riggs wrote:
> > New chapter for Hash Indexes, designed to help users understand how
> > they work and when to use them.
> >
> > Mostly newly written, but a few paras lifted from README when they were helpful.
>
>
..
> + the column value also makes all hash index scans lossy. Hash indexes may
> + take part in bitmap index scans and backward scans.
>
> Isn't it more correct to say that it must use a bitmap scan?
>
Why? Hash indexes do support regular index scan.
--
With Regards,
Amit Kapila.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2021-06-22 05:31:34 | Re: Detecting File Damage & Inconsistencies |
| Previous Message | Thomas Munro | 2021-06-22 05:02:46 | subscription/t/010_truncate.pl failure on desmoxytes in REL_13_STABLE |