>
> Do you know a workaround to do this ?
>
I just succeeded adding the following code:
FOR rec IN EXECUTE 'EXPLAIN ANALYZE ' || sSQL LOOP
RAISE NOTICE ' - %', rec;
END LOOP;
Regards,
Sabin
---(end of broadcast)---
TIP 9: In versions be
On Tue, 14 Sep 2004, Robert Davis wrote:
> I'm trying to benchmark some complex sql queries. One query, in
> particular, is causing problems -- its cost values can vary from 228
> to 907, its Total Runtimes from 60 ms to 5176 ms. The query plans
> show that the optimizer is choosing different pl
Are you forcing stuff out of cache (both postgres and OS) ? I've found that this can
make a huge difference with some queries ... not sure that this would make it have
different plans, though.
My ill-informied $0.02 worth ... fwiw
Greg Williamson
DBA
GlobeXplorer LLC
-Original Message
Dear Marian,
in postgresql 7.3 explain commands retruns as
set of rows.
The result of EXPLAIN can just be fecthed as result
of any other SELECT query and manipulated further.
i hope it helps.
sorry if i did not get ur problem rite.
regds
mallah.
On Friday 21 Mar 2003 11:51 am, Popeanga
Josh Berkus <[EMAIL PROTECTED]> writes:
>> db=#explain vacuum;
>> to return:
>> NOTICE: "vacuum" is an internal postgresql feature.
>> instead of:
>> ERROR: parser: parse error at or near "vacuum" at character 9
> No, it would not.
Actually, it's a fair question considering that the 7.3 man pag
