Thread: Execute arbitrary SQL queries does not come up in pgAdmin

Execute arbitrary SQL queries does not come up in pgAdmin

From
Edgar Sepulveda
Date:
Hi

I have installed pgAdmin3 version 1.12.2 and I have the problem that the option to execute SQL queries does not come up, instead pgAdmin3 goes frozen.

I am using a MacBook Pro with Mac OS X version 10.6.6, the database is postgresql version 9.0.3. I already uninstalled all software related with postgresql and pgAdmin and installed again but I still have the same problem.

I really appreciate any help to make this application work because I found it very productive for my job.

Thanks
Edgar Sepulveda

Re: Execute arbitrary SQL queries does not come up in pgAdmin

From
Claudio Freire
Date:
On Fri, Mar 18, 2011 at 4:00 PM, Edgar Sepulveda
<esepulveda@jigsawtech.com> wrote:
> Hi
> I have installed pgAdmin3 version 1.12.2 and I have the problem that the
> option to execute SQL queries does not come up, instead pgAdmin3 goes
> frozen.
> I am using a MacBook Pro with Mac OS X version 10.6.6, the database is
> postgresql version 9.0.3. I already uninstalled all software related with
> postgresql and pgAdmin and installed again but I still have the same
> problem.
> I really appreciate any help to make this application work because I found
> it very productive for my job.
> Thanks
> Edgar Sepulveda

A coworker of mine has the exact same issue (whenever he tries to
launch que query tool in 1.12.2 against both postgres 9.0.3 and 8.3.7
pgadmin freezes), but he's not running Mac OS, rather Windows Vista.

Furthermore, it started happening after some windows update - before
that update, pgadmin worked fine.

Older versions of pgadmin (I think 1.10) don't have the freezing
issue, but they don't work against postgres 9.0


Re: Execute arbitrary SQL queries does not come up in pgAdmin

From
Edgar Sepulveda
Date:
Hi 

These are the messages that the console displays:

3/18/11 4:55:43 PM pgAdmin3[513] kCGErrorIllegalArgument: CGSGetWindowBounds: NULL window
3/18/11 4:55:43 PM pgAdmin3[513] kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
3/18/11 4:55:43 PM [0x0-0x28028].org.postgresql.pgadmin[513] Fri Mar 18 16:55:43 Edgar-Sepulveda.local pgAdmin3[513] <Error>: kCGErrorIllegalArgument: CGSGetWindowBounds: NULL window
3/18/11 4:55:43 PM [0x0-0x28028].org.postgresql.pgadmin[513] Fri Mar 18 16:55:43 Edgar-Sepulveda.local pgAdmin3[513] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
3/18/11 4:56:15 PM [0x0-0x28028].org.postgresql.pgadmin[513] /Users/esepulveda/.pgadmin_histoqueries:1: parser error : Extra content at the end of the document
3/18/11 4:56:15 PM [0x0-0x28028].org.postgresql.pgadmin[513] ^

Thanks
Edgar Sepulveda

On Fri, Mar 18, 2011 at 12:09 PM, Claudio Freire <klaussfreire@gmail.com> wrote:
On Fri, Mar 18, 2011 at 4:00 PM, Edgar Sepulveda
<esepulveda@jigsawtech.com> wrote:
> Hi
> I have installed pgAdmin3 version 1.12.2 and I have the problem that the
> option to execute SQL queries does not come up, instead pgAdmin3 goes
> frozen.
> I am using a MacBook Pro with Mac OS X version 10.6.6, the database is
> postgresql version 9.0.3. I already uninstalled all software related with
> postgresql and pgAdmin and installed again but I still have the same
> problem.
> I really appreciate any help to make this application work because I found
> it very productive for my job.
> Thanks
> Edgar Sepulveda

A coworker of mine has the exact same issue (whenever he tries to
launch que query tool in 1.12.2 against both postgres 9.0.3 and 8.3.7
pgadmin freezes), but he's not running Mac OS, rather Windows Vista.

Furthermore, it started happening after some windows update - before
that update, pgadmin worked fine.

Older versions of pgadmin (I think 1.10) don't have the freezing
issue, but they don't work against postgres 9.0

Re: Execute arbitrary SQL queries does not come up in pgAdmin

From
Dave Page
Date:
On Sat, Mar 19, 2011 at 12:03 AM, Edgar Sepulveda
<esepulveda@jigsawtech.com> wrote:
> Hi
> These are the messages that the console displays:
> 3/18/11 4:55:43 PM pgAdmin3[513] kCGErrorIllegalArgument:
> CGSGetWindowBounds: NULL window
> 3/18/11 4:55:43 PM pgAdmin3[513] kCGErrorFailure: Set a breakpoint @
> CGErrorBreakpoint() to catch errors as they are logged.
> 3/18/11 4:55:43 PM [0x0-0x28028].org.postgresql.pgadmin[513] Fri Mar 18
> 16:55:43 Edgar-Sepulveda.local pgAdmin3[513] <Error>:
> kCGErrorIllegalArgument: CGSGetWindowBounds: NULL window
> 3/18/11 4:55:43 PM [0x0-0x28028].org.postgresql.pgadmin[513] Fri Mar 18
> 16:55:43 Edgar-Sepulveda.local pgAdmin3[513] <Error>: kCGErrorFailure: Set a
> breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
> 3/18/11 4:56:15 PM [0x0-0x28028].org.postgresql.pgadmin[513]
> /Users/esepulveda/.pgadmin_histoqueries:1: parser error : Extra content at
> the end of the document
> 3/18/11 4:56:15 PM [0x0-0x28028].org.postgresql.pgadmin[513] ^

Try deleting /Users/esepulveda/.pgadmin_histoqueries and then trying again.

-- 
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


Re: Execute arbitrary SQL queries does not come up in pgAdmin

From
Edgar Sepulveda
Date:
Thanks

It works now.

Edgar Sepulveda

On Fri, Mar 18, 2011 at 5:50 PM, Dave Page <dpage@pgadmin.org> wrote:
On Sat, Mar 19, 2011 at 12:03 AM, Edgar Sepulveda
> These are the messages that the console displays:
> 3/18/11 4:55:43 PM pgAdmin3[513] kCGErrorIllegalArgument:
> CGSGetWindowBounds: NULL window
> 3/18/11 4:55:43 PM pgAdmin3[513] kCGErrorFailure: Set a breakpoint @
> CGErrorBreakpoint() to catch errors as they are logged.
> 3/18/11 4:55:43 PM [0x0-0x28028].org.postgresql.pgadmin[513] Fri Mar 18
> 16:55:43 Edgar-Sepulveda.local pgAdmin3[513] <Error>:
> kCGErrorIllegalArgument: CGSGetWindowBounds: NULL window
> 3/18/11 4:55:43 PM [0x0-0x28028].org.postgresql.pgadmin[513] Fri Mar 18
> 16:55:43 Edgar-Sepulveda.local pgAdmin3[513] <Error>: kCGErrorFailure: Set a
> breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
> 3/18/11 4:56:15 PM [0x0-0x28028].org.postgresql.pgadmin[513]
> /Users/esepulveda/.pgadmin_histoqueries:1: parser error : Extra content at
> the end of the document
> 3/18/11 4:56:15 PM [0x0-0x28028].org.postgresql.pgadmin[513] ^

Try deleting /Users/esepulveda/.pgadmin_histoqueries and then trying again.

--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company