Hi All,
I'm looking for suggestions:
What kind of metrics would be beneficial to monitor and alert on Postgres
RDS while switching to GP3 volumes (from existing GP2 volumes)?
- We see intermittent I/O (disk queue depth) alerts with the existing GP2
storage type and burst credit alerts.
https://a
On Fri, Nov 18, 2022 at 3:55 PM Tom Lane 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
On Fri, Nov 18, 2022 at 2:23 PM Tomas Vondra
wrote:
> That is, when comparing costs, we require the cost to be at least 1%,
> because we have a cheapest path, and we're checking if it's worth
> building another one (which is not free - we have to allocate stuff
> etc.). And if the difference is ti
Tomas Vondra writes:
> On 11/18/22 13:15, Luca Ferrari wrote:
>> I've a table with a numeric column (integer), and I've created two
>> indexes on such column, one btree and one hash. The hash results much
>> larger as the btree, but what puzzles me is that executing an equality
>> simple query, th
On 11/18/22 13:15, Luca Ferrari wrote:
> Hi all,
> I'm just having a doubt about the choice of the planner for a small
> example table.
> I've a table with a numeric column (integer), and I've created two
> indexes on such column, one btree and one hash. The hash results much
> larger as the btree,
Hi all,
I'm just having a doubt about the choice of the planner for a small
example table.
I've a table with a numeric column (integer), and I've created two
indexes on such column, one btree and one hash. The hash results much
larger as the btree, but what puzzles me is that executing an equality
