From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Barry Lind <barry(at)xythos(dot)com> |
Cc: | Neil Conway <nconway(at)klamath(dot)dyndns(dot)org>, Ashley Cambrell <ash(at)freaky-namuh(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: 7.3 schedule |
Date: | 2002-04-11 20:48:43 |
Message-ID: | 18125.1018558123@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Barry Lind <barry(at)xythos(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Barry Lind | 2002-04-11 20:56:12 | Re: 7.3 schedule |
Previous Message | Tom Lane | 2002-04-11 20:23:30 | Re: Implicit coercions need to be reined in |