Re: On disable_cost - Mailing list pgsql-hackers

From Robert Haas
Subject Re: On disable_cost
Date
Msg-id CA+TgmobuPzMHUp11O9PP2tMBE_pse8p5J5_829eHEpZd0uibAg@mail.gmail.com
Whole thread Raw
In response to Re: On disable_cost  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: On disable_cost
List pgsql-hackers
On Fri, Aug 23, 2024 at 1:26 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> It looks like amcostestimate could change the path's disabled_nodes
> count, since that's set up before invoking amcostestimate.  I guess
> it could be set to INT_MAX to have a comparable solution to before.

It's probably better to add a more modest value, to avoid overflow.
You could add a million or so and be far away from overflow while
presumably still being more disabled than any other path.

--
Robert Haas
EDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: On disable_cost
Next
From: Tom Lane
Date:
Subject: Re: On disable_cost