On Wed, Jan 19, 2011 at 7:10 PM, Tom Lane wrote:
> frank joerdens writes:
>> I was just experimenting with debug logging on 8.3 and am finding that
>> I can't get it to log the table names involved in a given query, it
>> will always print the table alias used in your join instead, e.g.
>
> I don
frank joerdens writes:
> I was just experimenting with debug logging on 8.3 and am finding that
> I can't get it to log the table names involved in a given query, it
> will always print the table alias used in your join instead, e.g.
I don't know why you think that debug_print_plan is meant to do
Aha you are right. I tried this but set log min error statement
instead and so *that* didn't work.
Setting the right variable worked and I can now see the plan.
Thanks!!
--elein
On Wed, Mar 23, 2005 at 01:05:30PM -0700, Michael Fuhr wrote:
> On Wed, Mar 23, 2005 at 11:38:21AM -0800, elein wrote:
[EMAIL PROTECTED] (elein) writes:
> I cannot get debug_print_plan to print the query plan to the
> log.
/*
* Print plan if debugging.
*/
if (Debug_print_plan)
elog_node_display(DEBUG1, "plan", plan, Debug_pretty_print);
Looks like you also need to
On Wed, Mar 23, 2005 at 11:38:21AM -0800, elein wrote:
>
> I cannot get debug_print_plan to print the query plan to the
> log. I have set it in the postgresql.conf file and bounced
> the server. The output is simply not there. show shows
> that the value is set, but no output.
What's your log_
On Dec 29, 2004, at 3:16 PM, Tom Lane wrote:
Eric Brown <[EMAIL PROTECTED]> writes:
On Dec 29, 2004, at 2:28 PM, Tom Lane wrote:
Eric Brown <[EMAIL PROTECTED]> 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 j
Eric Brown <[EMAIL PROTECTED]> writes:
> On Dec 29, 2004, at 2:28 PM, Tom Lane wrote:
>> Eric Brown <[EMAIL PROTECTED]> 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
On Dec 29, 2004, at 2:28 PM, Tom Lane wrote:
Eric Brown <[EMAIL PROTECTED]> 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: par
Eric Brown <[EMAIL PROTECTED]> 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
DEBUG: StartTransactionCommand
LOG: statement: select 2+2;
DEBUG: p
