Re: BUG #15383: Join Filter cost estimation problem in 10.5

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: David Rowley <david(dot)rowley(at)2ndquadrant(dot)com>
Cc: Marko Tiikkaja <marko(at)joh(dot)to>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #15383: Join Filter cost estimation problem in 10.5
Date: 2019-04-03 17:07:41
Message-ID: 26761.1554311261@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

I wrote:
> I think we'd have to redesign those cost calculations completely to
> get ideal answers, and I don't especially want to do that right now.
> So I'm wondering about the attached as a stopgap. It seems like it's
> an improvement over what we have, even if not a full fix.

> Thoughts?

Ping? If nobody has any further ideas here, I'm going to clean up
the regression test issue and push this.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Jerry Sievert 2019-04-03 17:30:15 Re: Bug report - incorrect value displayed in jsonb column for large numbers
Previous Message Tom Lane 2019-04-03 16:48:10 Re: Bug report - incorrect value displayed in jsonb column for large numbers