From: | Eric Brown <eric(dot)brown(at)propel(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: debug_print_plan (pg7.4) doesn't seem to do anything |
Date: | 2004-12-30 01:04:27 |
Message-ID: | C0A4E4F2-59FE-11D9-AD0C-000A95C7176C@propel.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Dec 29, 2004, at 3:16 PM, Tom Lane wrote:
> Eric Brown <eric(dot)brown(at)propel(dot)com> writes:
>> On Dec 29, 2004, at 2:28 PM, Tom Lane wrote:
>>> Eric Brown <eric(dot)brown(at)propel(dot)com> writes:
>>>> I thought setting debug_print_plan was supposed to explain every
>>>> query
>>>> in my log file? I don't see the plan print either.
>>>
>>> No, it just prints the plan. With settings like yours I get
>
>> I don't get the the "DEBUG: parse tree:" or the DETAIL lines at all.
>
> [ scratches head... ] Are you sure debug_print_plan is really on?
> Check it with SHOW. It's hard to see why that debug output wouldn't
> get
> to the log if the rest of the debug messages do.
The problem was syslog. Postgresql logs to facility local0 by default
and I wasn't logging that at debug level.
From | Date | Subject | |
---|---|---|---|
Next Message | Horst G. Reiterer | 2004-12-30 05:11:04 | Roadmap for Database Kernel XA Support |
Previous Message | Tom Lane | 2004-12-29 23:30:42 | Re: pg_dump and pgpool |