Re: why choosing an hash index instead of the btree version even if the cost is lower?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: why choosing an hash index instead of the btree version even if the cost is lower?
From: Luca Ferrari <fluca1978@xxxxxxxxx>
Date: Fri, 18 Nov 2022 17:17:55 +0100
Cc: Tomas Vondra <tomas.vondra@xxxxxxxxxxxxxxxx>, postgres performance list <pgsql-performance@xxxxxxxxxxxxxx>
In-reply-to: <2186064.1668783312@sss.pgh.pa.us>
References: <CAKoxK+4ygm7hwRqVNgG9-Zge-sbN5kQfG_Zri9_Nxw7MF+35FA@mail.gmail.com> <52c1cb75-89bc-61c4-2ec9-42c683ba8f14@enterprisedb.com> <2186064.1668783312@sss.pgh.pa.us>

On Fri, Nov 18, 2022 at 3:55 PM Tom Lane <tgl@xxxxxxxxxxxxx> wrote:
> Even more to the point: if the total costs are fuzzily the same,
> then the next point of comparison will be the startup costs,
> which is where the hash index wins.

Thanks, it is clear now.

Luca

References:
- why choosing an hash index instead of the btree version even if the cost is lower?
  - From: Luca Ferrari
- Re: why choosing an hash index instead of the btree version even if the cost is lower?
  - From: Tomas Vondra
- Re: why choosing an hash index instead of the btree version even if the cost is lower?
  - From: Tom Lane

Prev by Date: Re: why choosing an hash index instead of the btree version even if the cost is lower?
Next by Date: Need suggestion to set-up RDS alerts on GP3 volumes
Previous by thread: Re: why choosing an hash index instead of the btree version even if the cost is lower?
Next by thread: Re: why choosing an hash index instead of the btree version even if the cost is lower?
Index(es):
- Date
- Thread

[Postgresql General] [Postgresql PHP] [PHP Users] [PHP Home] [PHP on Windows] [Kernel Newbies] [PHP Classes] [PHP Books] [PHP Databases] [Yosemite]

Powered by Linux