Re: Error "column not found in pgSet: current_query"

From: Guillaume Lelarge <guillaume(at)lelarge(dot)info>
To: Colin Beckingham <colbec(at)start(dot)ca>
Cc: pgadmin-support(at)postgresql(dot)org
Subject: Re: Error "column not found in pgSet: current_query"
Date: 2012-02-24 23:23:14
Message-ID: 1330125794.2276.16.camel@localhost.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-support

On Fri, 2012-02-24 at 06:35 -0500, Colin Beckingham wrote:
> Using OpenSUSE 12.1, latest 1.15 Dev
>
> (NTF, did a git pull to update my source install this morning and had to
> do a "bash bootstrap" to get rid of make errors. Works ok now.)
>
> After click on 'server status' pgadmin warned me that I did not have
> server instrumentation installed. I went to yast and installed the
> postgresql-contrib and restarted the postgresql server. This allowed the
> button "Fix it" to appear and I clicked this. Now I no longer get the
> warnings that I have no instrumentation installed.
>
> Now, on click 'server status' I go straight to server status window, but
> this is overlaid by a message box "column not found in pgSet:
> current_query". Repeated clicks on OK in msg box have no effect.
> Repeated clicks on the server status window X control eventually bring
> up a 'Force quit' dialog which allows me to stop the application.
>

Oops, my mistake. Sorry about this. The fix will be pushed in a few
minutes.

--
Guillaume
http://blog.guillaume.lelarge.info
http://www.dalibo.com

In response to

Browse pgadmin-support by date

  From Date Subject
Next Message Guillaume Lelarge 2012-02-24 23:26:12 Re: Failed to write to history file
Previous Message michel boekestein 2012-02-24 13:43:09 Failed to write to history file