Re: [pgadmin-support] Debugger freeze

2016-02-17 Thread Stefan Stefanov
korry.doug...@enterprisedb.com >Относно: Re: [pgadmin-support] Debugger freeze >До: Stefan Stefanov >Изпратено на: 15.02.2016 23:30 Like Dave, I am not able to replicate the problem. However, I tested with a Linux version of the database server and a Linux

Re: [pgadmin-support] Debugger freeze

2016-02-16 Thread Dave Page
On Mon, Feb 15, 2016 at 9:30 PM, Korry Douglas < korry.doug...@enterprisedb.com> wrote: > > Like Dave, I am not able to replicate the problem. However, I tested with > a Linux version of the database server and a Linux version of pgAdmin. > > Dave, did you test on Windows or Linux? > I tested on

Re: [pgadmin-support] Debugger freeze

2016-02-16 Thread Stefan Stefanov
Korry, I used EDB graphic installer. Sincerely, Stefan > Оригинално писмо >От: Korry Douglas korry.doug...@enterprisedb.com >Относно: Re: [pgadmin-support] Debugger freeze >До: Stefan Stefanov >Изпратено на: 15.02.2016 23:30

Re: [pgadmin-support] Debugger freeze

2016-02-16 Thread Korry Douglas
uglas korry.doug...@enterprisedb.com >Относно: Re: [pgadmin-support] Debugger freeze >До: Dave Page >Изпратено на: 15.02.2016 18:01 As Dave mentioned, the interesting error message is probably this one: could not find block containing chunk 01176B70 That error occurs when the dat

Re: [pgadmin-support] Debugger freeze

2016-02-16 Thread Stefan Stefanov
on could be made because the target machine actively refused it. Sincerely, Stefan > Оригинално писмо ---- >От: Dave Page dp...@pgadmin.org >Относно: Re: [pgadmin-support] Debugger freeze >До: Stefan

Re: [pgadmin-support] Debugger freeze

2016-02-16 Thread Stefan Stefanov
enterprisedb.com >Относно: Re: [pgadmin-support] Debugger freeze >До: Dave Page >Изпратено на: 15.02.2016 18:01 As Dave mentioned, the interesting error message is probably this one: could not find block containing chunk 01176B7

Re: [pgadmin-support] Debugger freeze

2016-02-15 Thread Korry Douglas
from client: No connection could be made because the target machine actively refused it. Sincerely, Stefan > Оригинално писмо >От: Dave Page dp...@pgadmin.org <mailto:dp...@pgadmin.org> >Относно: Re: [pgadmin-support] Debugger freeze >

Re: [pgadmin-support] Debugger freeze

2016-02-15 Thread Dave Page
6:02 EET STATEMENT: SELECT * FROM pldbg_abort_target(1) > 2016-02-13 16:06:02 EET FATAL: connection to client lost > 2016-02-13 16:06:02 EET LOG: could not receive data from client: No > connection could be made because the target machine actively refused it. > > > > Sincere

Re: [pgadmin-support] Debugger freeze

2016-02-13 Thread Stefan Stefanov
> Оригинално писмо >От: 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...@

Re: [pgadmin-support] Debugger freeze

2016-02-12 Thread Dave Page
Hi On Thu, Feb 11, 2016 at 6:36 PM, Stefan Stefanov 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

[pgadmin-support] Debugger freeze

2016-02-11 Thread Stefan Stefanov
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 playgr