From: | Shigeru Hanada <shigeru(dot)hanada(at)gmail(dot)com> |
---|---|
To: | HuangQi <huangqiyx(at)gmail(dot)com> |
Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: debugging tools inside postgres |
Date: | 2011-06-24 12:53:51 |
Message-ID: | 4E0488DF.2040801@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
(2011/06/24 19:14), HuangQi wrote:
> 2011/6/24 Shigeru Hanada<shigeru(dot)hanada(at)gmail(dot)com>
>
>> (2011/06/24 15:35), HuangQi wrote:
>> ex)
>> elog(DEBUG1, "%s", nodeToString(plan));
>
> Hi,
> I don't know why but when I am debugging the query evaluation, the elog
> function can not output to shell.
What kind of tool do you use to execute the query to be evaluated?
If you are using an interactive tool such as psql, please check setting
of client_min_messages. Otherwise, please check settings of
log_destination, logging_collector and log_min_messages to ensure that
elog() prints debugging information into your server log file, or stderr
of the terminal which has been used to start PostgreSQL server.
Regards,
--
Shigeru Hanada
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2011-06-24 13:04:12 | Re: pg_upgrade defaulting to port 25432 |
Previous Message | Steve Singer | 2011-06-24 12:32:03 | Re: Online base backup from the hot-standby |