It just happened again. I ran a query in a window and after it completed I waited 10-15 minutes and ran it again. I got a connection error. I ran the query again (by hitting the green > icon) and it caused pgAdmin to crash.
Moreover, I was simultaneously running another tool that was connected to a non-Postgres database. After PgAdmin crashed I ran a query in the other tool. It ran fine. This implies that the connection isn't being dropped by my router due to inactivity. It is probably happening within the Postgres server. I will try to run this test again using PgAdmin and a different tool that can connect to the same Postgres database. On Wed, Nov 11, 2009 at 8:32 AM, Michael Shapiro <mshapir...@gmail.com>wrote: > It happens to me quite a lot, as well. I will lose the contents of the SQL > window as well when it happens. > > It would be good if PgAdmin would automatically try to reconnect (at least > once) before giving up. > > > On Wed, Nov 11, 2009 at 8:08 AM, Eugene Lisitsky <lisit...@gmail.com>wrote: > >> >> I see such problem when remote servers replies slowly. >> >> >> 2009/11/1 Pedro Doria Meunier <pdo...@netmadeira.com> >> >>> -----BEGIN PGP SIGNED MESSAGE----- >>> Hash: SHA1 >>> >>> Replying to self: >>> Altering the tcp_keepalive_time, tcp_keepalive_intvl values *didn't* >>> solve the problem. >>> >>> >>> On 11/01/2009 03:04 PM, Pedro Doria Meunier wrote: >>> > >>> > Sorry forgot to tell it happens on a remote connection... :) >>> > >>> > This is AFAICS is most probably a timeout problem. It makes me >>> > wonder if my router isn't dropping idle connections... >>> > >>> > Anyway I'm playing with tcp_keepalive_time, tcp_keepalive_intvl >>> > values to see if it solves the problem. btw: tcp_keepalive_time = >>> > 75 tcp_keepalive_intvl = 60 >>> > >>> > >>> > I'll post my results. >>> > >>> > BR, Pedro Doria Meunier >>> > >>> > >>> > On 11/01/2009 12:37 PM, Dave Page wrote: >>> >> On Sun, Nov 1, 2009 at 11:04 AM, Pedro Doria Meunier >>> >> <pdo...@netmadeira.com> wrote: >>> >>> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 >>> >>> >>> >>> Hi, >>> >>> >>> >>> pgAdmin ver 1.10.0 rev. 7945:7946 freezes after a short time >>> >>> of inactivity... Fedora 11 - kernel 2.6.30.9-90.fc11.i686.PAE >>> >>> >>> >>> Reproducible by: - - connect to a db - - click on any of the >>> >>> db's objects - - wait a while (1-3 minutes) - - refresh the >>> >>> object >>> >>> >>> >>> kaboom. it freezes. have to force termination. >>> > >>> >> I only have 64 bit CentOS 5 here at the moment, but I can't >>> >> reproduce on that. Anyone else? >>> > >>> >>> Setting the log to "debug" offers no joy as to discover the >>> >>> cause... >>> >>> >>> >>> I'm unsure as if it's a pgAdmin problem or rather a connection >>> > timeout... >>> >>> At any rate... does pgAdmin make any attempt to KEEP_ALIVE >>> >>> (the connection)? >>> > >>> >> No. >>> > >>> -----BEGIN PGP SIGNATURE----- >>> Version: GnuPG v1.4.9 (GNU/Linux) >>> Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ >>> >>> iEYEARECAAYFAkrtq3EACgkQ2FH5GXCfxAuPUQCdExxsfhj3pyrCXuK0MqB0Sm9w >>> xsIAoI3N5xHOiHlGQC6HfW2BtPXpTtlt >>> =gNcZ >>> -----END PGP SIGNATURE----- >>> >>> >>> -- >>> >>> Sent via pgadmin-support mailing list (pgadmin-support@postgresql.org) >>> To make changes to your subscription: >>> http://www.postgresql.org/mailpref/pgadmin-support >>> >> >> >> >> -- >> Yours, >> Eugene Lisitsky >> > >
