From: | Chuck McDevitt <cmcdevitt(at)greenplum(dot)com> |
---|---|
To: | Julius Tuskenis <julius(dot)tuskenis(at)gmail(dot)com>, "pgadmin-hackers(at)postgresql(dot)org" <pgadmin-hackers(at)postgresql(dot)org> |
Subject: | Re: reconnecting to DB after connection break |
Date: | 2009-08-21 20:05:42 |
Message-ID: | 2106D8DC89010842BABA5CD03FEA40610100FB8145@EXVMBX018-10.exch018.msoutlookonline.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
> -----Original Message-----
> From: pgadmin-hackers-owner(at)postgresql(dot)org [mailto:pgadmin-hackers-
> owner(at)postgresql(dot)org] On Behalf Of Julius Tuskenis
> Sent: Friday, August 21, 2009 3:16 AM
> To: pgadmin-hackers(at)postgresql(dot)org
> Subject: [pgadmin-hackers] reconnecting to DB after connection break
>
> Hello,
>
> I'm thinking of changing pgAdmin so it would try to reconnect after its
> connection to server breaks. Is that ok with you? Maybe theres someone
> already dealing with the problem.
>
> I think I could change pgConn::ExecuteVoid, pgConn::ExecuteScalar and
> pgConn::ExecuteSet methods so on connection to DB error there would be
> an attempt to reconnect. If someone knows a better solution - please,
> share it. :)
>
> I'm new here so maybe someone would advice what "pitfalls" to avoid.
>
> --
> Julius Tuskenis
>
Sounds like a good idea. The one pitfall I see is that any temporary tables the session had disappear when you disconnect and reconnect, but I don't think there is anything to be done about that.
From | Date | Subject | |
---|---|---|---|
Next Message | Guillaume Lelarge | 2009-08-21 20:45:36 | Re: reconnecting to DB after connection break |
Previous Message | Ângelo Marcos Rigo | 2009-08-21 11:05:03 |