Re: Plan stability versus near-exact ties in cost estimates

From: "Albe Laurenz" <laurenz(dot)albe(at)wien(dot)gv(dot)at>
To: "Tom Lane *EXTERN*" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Plan stability versus near-exact ties in cost estimates
Date: 2012-04-20 15:29:34
Message-ID: D960CB61B694CF459DCFB4B0128514C207C343ED@exadv11.host.magwien.gv.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane wrote:
>> What if you remove the exact cost comparison, but leave the part
where
>> old dominates new based on rows?
>
> Um, that is what the proposed patch does.

I was referring to the first two lines that the patch removes.
I guess I don't understand why they should go.

Anyway, I fail to see how this patch could introduce new
platform-specific
instabilities, so it seems safe for me.

Yours,
Laurenz Albe

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2012-04-20 15:30:07 Re: Plan stability versus near-exact ties in cost estimates
Previous Message Simon Riggs 2012-04-20 15:20:25 Re: New sync commit mode remote_write