Re: 7.3 schedule
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Barry Lind <barry@xythos.com>
Cc: Neil Conway <nconway@klamath.dyndns.org>, Ashley Cambrell <ash@freaky-namuh.com>, pgsql-hackers@postgresql.org
Date: 2002-04-11T20:48:43Z
Lists: pgsql-hackers
Barry Lind <barry@xythos.com> writes: > ... > Since we > don't currently provide any information to the user on the relative cost > of the parse, plan and execute phases, the end user is going to be > guessing IMHO. You can in fact get that information fairly easily; set show_parser_stats, show_planner_stats, and show_executor_stats to 1 and then look in the postmaster log for the results. (Although to be fair, this does not provide any accounting for the CPU time expended simply to *receive* the query string, which might be non negligible for huge queries.) It would be interesting to see some stats for the large-BLOB scenarios being debated here. You could get more support for the position that something should be done if you had numbers to back it up. regards, tom lane