Hi Dave,
I think that suffering from network disconnections is unlikely because the
test Postgres server is on localhost. No trouble with it that I have noticed.
Here is what I found in pgadmin.log for the time that I was preparing the
failure case.
2016-02-10 23:47:19 ERROR
: select() failed waiting for target
2016-02-11 00:00:54 ERROR
: select() failed waiting for target
2016-02-11 20:13:44 ERROR
: select() failed
for target
2016-02-11 21:36:37 ERROR
: ERROR:
select()waiting failed waiting for target
2016-02-11 21:37:03 ERROR
:
Hope this helps.
Sincerely,
Stefan
>-------- Оригинално писмо --------
>От: Dave Page dp...@pgadmin.org
>Относно: Re: [pgadmin-support] Debugger freeze
>До: Stefan Stefanov
>Изпратено на: 12.02.2016 15:45
Hi
On Thu, Feb 11, 2016 at 6:36 PM, Stefan Stefanov
stefanov...@abv.bg > wrote:
Dear Sir or Madam,
I am writing to report a bug in pgadmin III 1.22.0 running on Windows 7 x64
connected to PostgreSQL 9.5.0 VC++ build 1800, 64 bit.
To reproduce the bug create this trivial function using SQL query editor. The
example is in "playground" schema.
create function playground.dbg_test() returns void as
$$
declare
i integer;
t text;
begin
for i in 1 .. 100 loop
t := 'XYZ' || to_char(i, '999');
raise notice 'Round %', t;
end loop;
end;
$$ language plpgsql;
Right-click the function in Object browser then debug. Step a few times
through the loop then take some time doing other things in pgadmin iii (browse
data, run queries etc.) then return to the debug window and step again a few
times. The debug window usually freezes (debug.png).
Two locks remain (server status.png). The server may be cleared by cancelling
the query of the global listener (pid 7748 in the example) but then pgadmin
windows
stop responding.
This is preventing me from using the debugger and I need it badly.
I've tried to reproduce this but am unable, even letting my machine go
into powersave mode while the function is running.
Can anyone else reproduce?
Stefan, could it be that you're suffering from network disconnections?
pgAdmin 3 really doesn't like them, and unfortunately it's a hard problem to
fix given the current code structure (it's one of the things we're fixing in
pgAdmin 4 which is completely new).
--
Dave Page
Blog:
http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK:
http://www.enterprisedb.com
The Enterprise PostgreSQL Company
