Re: Proposed patch to make mergejoin cost estimationmore symmetric - Mailing list pgsql-patches

From Gregory Stark
Subject Re: Proposed patch to make mergejoin cost estimationmore symmetric
Date
Msg-id 87tzmtoeqp.fsf@oxford.xeocode.com
Whole thread Raw
In response to Re: Proposed patch to make mergejoin cost estimation more symmetric  (Simon Riggs <simon@2ndquadrant.com>)
List pgsql-patches
"Simon Riggs" <simon@2ndquadrant.com> writes:

> I think we all accept that you're the master here. The question is how
> will we know to report problems to you?

Hm, I think I agree. The problem is where to draw the line. Ultimately
everything in the statistics tables and more could potentially be relevant.

The other problem is that currently our explain output is a bit of a hack.
It's just text we print out and we're limited in how much data we can put in
that without it being unwieldy.

When we get the table-based or xml-based or some other machine-readable
explain plan we could stuff a lot more data in there and have it be the UI's
responsibility to decide what data to display.

When that happens it would be nice to have the raw data used to generate the
cost estimations. At least the most important factors.

--
  Gregory Stark
  EnterpriseDB          http://www.enterprisedb.com
  Ask me about EnterpriseDB's RemoteDBA services!

pgsql-patches by date:

Previous
From: xeb@mail.ru
Date:
Subject: [PATCH] automatic integer conversion
Next
From: Alvaro Herrera
Date:
Subject: Re: [PATCH] automatic integer conversion