Re: On disable_cost - Mailing list pgsql-hackers

From Andres Freund
Subject Re: On disable_cost
Date
Msg-id 20191101160038.wn3qkvp4psnatmm3@alap3.anarazel.de
Whole thread Raw
In response to Re: On disable_cost  (Thomas Munro <thomas.munro@gmail.com>)
Responses Re: On disable_cost  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Hi,

On 2019-11-01 19:58:04 +1300, Thomas Munro wrote:
> On Fri, Nov 1, 2019 at 7:42 PM Zhenghua Lyu <zlv@pivotal.io> wrote:
> >     It is tricky to set disable_cost a huge number. Can we come up with better solution?
> 
> What happens if you use DBL_MAX?

That seems like a bad idea - we add the cost multiple times. And we
still want to compare plans that potentially involve that cost, if
there's no other way to plan the query.

- Andres



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: WIP/PoC for parallel backup
Next
From: Igor Calabria
Date:
Subject: Re: Adding percentile metrics to pg_stat_statements module