dpage@postgresql.org wrote:
>> ------- Original Message -------
>> From: Erwin Brandstetter <brandstetter@falter.at>
>> To: dpage@postgresql.org
>> Sent: 05/06/07, 21:28:52
>> Subject: Re: [pgadmin-hackers] Testing 1.7: Errors with function pldbg_get_target_info(..)
>>
>> dpage@postgresql.org wrote:
>>
>>> Erwin Brandstetter wrote:
>>>
>>>
>>>> Hi developers! Hi Dave!
>>>>
>>>> Still testing pgAdmin III 1.7.0, rev 6292:6293. Client Win XP, hosts:
>>>> Debian Sarge / PG 8.1.8 and Debian Etch / PG 8.2.3 (and looking forward
>>>> to the snapshot to come)
>>>>
>>>>
>>>> I found multiple occurrences of this mysterious error message in my
>>>> logs. while testing pgAdmin3 1.7 (with pg 8.1.8 server). A quick google
>>>> search has found the string 'pldbg_get_target_info' in pgAdmin source
>>>> code...
>>>>
>>>> FEHLER: Funktion pldbg_get_target_info("unknown", "unknown") existiert
>>>> nicht
>>>> TIPP: ....
>>>> ANWEISUNG: SELECT * FROM pldbg_get_target_info('version', 'f');
>>>>
>>>> Translates:
>>>> ERROR: Function pldbg_get_target_info("unknown", "unknown") does not exist
>>>> HINT: ...
>>>> STATEMENT: SELECT * FROM pldbg_get_target_info('version', 'f');
>>>>
>>> Thats a function in the debugger plugin. Are you seeing a Debug or
>>> Global Breakpoint menu option someplace where you probably shouldn't?
>>>
>> Not that I would have noticed. But if I know what to look for, I will
>> keep an eye open. I would have an item of the name "Debug" or "Global
>> Breakpoint" in some random menu?
>>
> On the tools menu, or treeview context menu, yes.

I think I have pinned this one down, at last: it happens when I open a
context menu on a any function (trigger or not) in the object tree for
the first time since connection. I do not get a "Debug" or "Global
Breakpoint" option in the menu, though. Neither do I get an error
message in the application. It only shows up in the log file. Seems like

Tested with pgAdmin III 1.8.0 Beta 1(Jul 13 2007, rev: 6423) on Win XP,
host: Debian Sarge / PG 8.1.8 and Debian Etch / PG 8.2.4.
Only these languages are installed: "internal", "c", "sql", "plpgsql".


Regards
Erwin

---------------------------(end of broadcast)---------------------------
TIP 5: don't forget to increase your free space map settings

Erwin Brandstetter wrote:
> I think I have pinned this one down, at last: it happens when I open a
> context menu on a any function (trigger or not) in the object tree for
> the first time since connection. I do not get a "Debug" or "Global
> Breakpoint" option in the menu, though. Neither do I get an error
> message in the application. It only shows up in the log file. Seems like
>
> Tested with pgAdmin III 1.8.0 Beta 1(Jul 13 2007, rev: 6423) on Win XP,
> host: Debian Sarge / PG 8.1.8 and Debian Etch / PG 8.2.4.
> Only these languages are installed: "internal", "c", "sql", "plpgsql".

It just clicked that you meant the error was in the server logs, and not
the pgAdmin log (where it's intentionally filtered). I've changed the
query to one that won't error, but I'm not 100% convinced it'll be so
effective so I respectfully reserve the right to roll it back in the
future :-)

Regards, Dave.


---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly

Hi Dave!

dpage@postgresql.org wrote:
> It just clicked that you meant the error was in the server logs, and
> not the pgAdmin log (where it's intentionally filtered). I've changed
> the query to one that won't error, but I'm not 100% convinced it'll be
> so effective so I respectfully reserve the right to roll it back in
> the future :-)

Effective or not, you seem to have nailed it. The error message has not
turned up again since beta2.

Regards
Erwin

---------------------------(end of broadcast)---------------------------
TIP 3: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq