Re: On disable_cost

From: Thomas Munro <thomas(dot)munro(at)gmail(dot)com>
To: Zhenghua Lyu <zlv(at)pivotal(dot)io>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: On disable_cost
Date: 2019-11-01 06:58:04
Message-ID: CA+hUKGJ0NTtLB5dv5gbuDoRirtamC--wWGNoAT4=fF2Ev1bRdA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Nov 1, 2019 at 7:42 PM Zhenghua Lyu <zlv(at)pivotal(dot)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?

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Eisentraut 2019-11-01 07:07:16 Refactor parse analysis of EXECUTE command
Previous Message Zhenghua Lyu 2019-11-01 06:42:25 On disable_cost