Re: pgAdmin crashes when client_min_messages is

From: Andreas Pflug <pgadmin(at)pse-consulting(dot)de>
To: mydeja(at)achimota(dot)com
Cc: pgadmin-support(at)postgresql(dot)org
Subject: Re: pgAdmin crashes when client_min_messages is
Date: 2003-12-22 11:13:59
Message-ID: 3FE6D1F7.9040100@pse-consulting.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers pgadmin-support pgsql-patches

My Deja wrote:

> I am trying to get some query trees to appear in the PostgreSQL log
> and in order to that I have set
> client_min_messages = DEBUG1 in order to use the following settings
> debug_print_parse, debug_print_rewritten, or debug_print_plan which
> are required for the query tree to show up in the log.
>
> pgAdmin crashes whenever I set that option. I tried a few times and I
> am sure of it.
> I am using PostgreSQL 7.4 under Cygwin on a Windows 2000 machine, but
> I don't think that has any relevance.

I can confirm this problem. Apparently the flood of debug notices will
kill pgAdmin3 after a while.
I'll have a deeper look into this later. Until then, do *not* set these
options in postgresql.conf. Instead, set these options per user (if you
want to observe a user *different* from the one you're using with
pgAdmin3), or set these options in the query tool prior to executing
your queries to inspect.

Regards,
Andreas

In response to

Responses

Browse pgadmin-hackers by date

  From Date Subject
Next Message Dave Page 2003-12-22 12:25:16 Server update
Previous Message Dave Page 2003-12-22 10:17:28 Server Upgrade

Browse pgadmin-support by date

  From Date Subject
Next Message Lauris Bukšis 2003-12-22 11:41:31 Problems with editor
Previous Message Dave Page 2003-12-22 10:15:49 Re: We just found another small bug in pgAdmin3

Browse pgsql-patches by date

  From Date Subject
Next Message Magnus Hagander 2003-12-22 14:45:23 Re: [HACKERS] Current Win32 port status
Previous Message Bruce Momjian 2003-12-22 08:23:02 Re: fork/exec patch: pgstat + BootstrapMain