Re: A bug to report

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: SETU SAXENA <seturockslp(at)gmail(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: A bug to report
Date: 2011-01-28 13:49:33
Message-ID: AANLkTiknFBuKRObxdhHoSbPD8g3FFg+-e9V0qysoq8e-@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, Jan 25, 2011 at 1:31 AM, SETU SAXENA <seturockslp(at)gmail(dot)com> wrote:
> To,
> the respective authority
> pgadmin
>
> Sub: to report a bug in posgresql version 1.10.2  (Aug 24 2010, rev 8217)
>
> This to inform you that we are using posgre sql (pgadmin) version mentioned
> above. We are using pgadmin to log on to a lnux server with the client
> applicaions on our lab systems.
> It has been repeatedly observed that whenever a connection to the sever is
> released/cut off the client app automatically gets closed( may be the
> procress gets dead/hang and the app gets closed)
>
> kindly see to the problem , we really love working on pgadmin but this bug
> removes all our status and all the query gets lost.
>
> Hope you will see to the matter.

I seem to remember something like this being reported before, but I
don't remember the details. You might try here:

http://archives.postgresql.org/pgadmin-support/

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Chris R. 2011-01-28 14:45:45 BUG #5854: base64 decode returns bytea and no text
Previous Message Robert Haas 2011-01-28 13:47:34 Re: BUG #5851: ROHS (read only hot standby) needs to be restarted manually in somecases.