>
> 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
Hi there,
I'd like to rise the performance of a custom function, but I read somewhere
I cannot use EXPLAIN ANALYZE to get the execution plan of the code from the
function.
Do you know a workaround to do this ?
I tried to apply EXPLAIN ANALYZE statements inside my procedure hopping I
will get
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
ssage-
From: Robert Davis [mailto:[EMAIL PROTECTED]
Sent: Tue 9/14/2004 6:21 PM
To: [EMAIL PROTECTED]
Cc:
Subject: [SQL] explain analyze results are different for each iteration
I'm trying to benchmark some complex sql queries. One query, in
particular, is causing probl
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 plans for different
iterations of the same query
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
hi.
I still go on looking for query time.
I get a question!
explain is a command that estimate cost of query time ok, but I don't
know how is the time.
for example:
mybase=> explain select * from tabla1;
NOTICE: QUERY PLAN:
Seq Scan on tabla1 (cost=0.00..1.06 r
Hello,
I'm looking for a better tutorial of how EXPLAIN works. I know Mr. Tom Lane
wrote a "quick & dirty explanation" and that "plan-reading is an art that
deserves a tutorial, and I haven't had time to write one". In which case I'd
like to know if there's any other tutorials/resources.
