Thread: BUG: PgAdminIII crashes when server closes the connection by idle time

H<br /> i guys,<br /><br /> I would like do report an ancient bug on PgAdminIII.<br /><br /> I'm using PgAdminIII
1.10.2on Ubuntu Lucid Kernel 2.6.32-25, that was installed by apt-get.<br /> The server is running the version 8.3.8 of
PostgreSQL.<br/><br /> Here I will reproduce the steps, and the prerequisites are only the server configured to kill
idleconnections from clients after X time.<br /> 1) With PgAdminIII opened, and connected in the database, open the
QueryTool, to make custom queries. <br /> 2) Make one, execute, and leave PgAdmin in second plan (minimized, for
example)for more than the X time, and keep the window open.<br /> 3) After the idle time, return to the window of
customquery, make one more query and execute.<br /> 4) At this time, in the Output Pane, in the tab Messages will
appearwritten only "********** Error **********".<br /> 5) Rerun the same query.<br /> 6) PgAdminIII closes
immediately.<br/><br /> In the ~/pgadmin.log is writen this:<br /><br /> 2010-09-15 16:36:21 ERROR  : Server closed
connectionunexpectedly.<br />         This probably means the server terminated abnormally<br />         before or
whileprocessing the request.<br /> 2010-09-15 16:36:24 ERROR  : no connection to the server.<br /><br /> To circumvent
theproblem, it would be interesting to test connectivity with the server before performing each query, and if  client
isdisconnected, reconnects to the database, then performs the query.<br /> Obviously this was only a hint, and it is up
toyou to decide how to handle this problem.<br /><br /> Tks for the attention.<br /><br /> Jeferson Rodrigues  

Hi

On Thu, Sep 23, 2010 at 12:48 PM, Jeferson Alberto Rodrigues
<jefersonal@celepar.pr.gov.br> wrote:
> H
> i guys,
>
> I would like do report an ancient bug on PgAdminIII.
>
> I'm using PgAdminIII 1.10.2 on Ubuntu Lucid Kernel 2.6.32-25, that was
> installed by apt-get.
> The server is running the version 8.3.8 of PostgreSQL.
>
> Here I will reproduce the steps, and the prerequisites are only the server
> configured to kill idle connections from clients after X time.
> 1) With PgAdminIII opened, and connected in the database, open the Query
> Tool, to make custom queries.
> 2) Make one, execute, and leave PgAdmin in second plan (minimized, for
> example) for more than the X time, and keep the window open.
> 3) After the idle time, return to the window of custom query, make one more
> query and execute.
> 4) At this time, in the Output Pane, in the tab Messages will appear written
> only "********** Error **********".
> 5) Rerun the same query.
> 6) PgAdminIII closes immediately.

Please test in 1.12.0 - there were various changes to make the code
more robust in the event of a connection drop.

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

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