On Mon, Jul 12, 2010 at 02:06:43PM +0800, Craig Ringer wrote:
> Meh, personally I'll stick to the good old profiling methods "is it fast
> enough", "\timing", and "explain analyze".
I agree. Some hint could be included in 'explain analyze' output, maybe just
to separate the timings for things that are well covered by the query plan
optimizer from those that aren't. I found this in a line like this:
Filter: (approved AND (NOT archived) AND ((time_to > now()) OR (time_to IS NULL)) AND ((time_from < now()) OR (time_from IS NULL)) AND usercandoonobject(1, 1, 'news'::bpchar, news_id))
These other referenced columns in the filter were all insignificant
(time-wise) compared to the single function call, but I had to find
that out with a manual search.
--
2. That which causes joy or happiness.
--
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
