Yes, we indeed get the cost of the plan at the first line itself. Somehow, I missed this point. We just in fact implemented this functionality and its working. Thanks again.
Srinivas Karthik V <skarthikv.iitb@gmail.com> writes: > Specifically, I have a Java program which calls > ResultSet rs = statement.executeQuery("explain select * from table"); > I would like to change PostgreSQL such that ResultSet rs should contain a > field that contains also the cost of the optimizer chosen plan.
Why do you need to change anything? The cost is right there in the first line of the result text. It might be easier to parse out if you use one of EXPLAIN's intended-to-be-machine-readable output formats, though.
Yeah - if we were going to do this at all, it'd want to be output that decomposes _all_ the explain output into columns. But since we can emit json, xml, etc, I don't really see the point.