Re: explain analyze of PG server level

debug_print_plan = true
can give "explain" info, but not "explain ANALYZE" info,
like
Seq Scan on tmp_user (cost=0.00..20.00 rows=1000 width=0) (actual
time=0.04..30164.59 rows=1019462 loops=1
which is most interesting to me.

Thanks,

-----Original Message-----
From: Joshua D. Drake [mailto:jd(at)commandprompt(dot)com]
Sent: Friday, March 25, 2005 10:26 AM
To: Lee Wu
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: [ADMIN] explain analyze of PG server level

On Fri, 2005-03-25 at 10:00 -0700, Lee Wu wrote:
> -->
>
> Hello,
>
>
>
> Is there a global PG server level explain analyze parameter I can turn
> on to catch
>
> all SQLs issued against PG server, like Oracle SQL_TRACE, and PG
> log_statement

Some of these options in the postgresql.conf might help you out:

#debug_print_parse = false
#debug_print_rewritten = false
#debug_print_plan = false
#debug_pretty_print = false

>
> in PG 7.3.2?
>
>
>
> Thanks,
>
>
>
>
>
>
--
Command Prompt, Inc., Your PostgreSQL solutions company. 503-667-4564
Custom programming, 24x7 support, managed services, and hosting
Open Source Authors: plPHP, pgManage, Co-Authors: plPerlNG
Reliable replication, Mammoth Replicator - http://www.commandprompt.com/