vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| I think Dave fixed one of the cases that caused this a few revs ago, but another one still remains. Steps to reproduce: In pgAdmin 1.4.2: * connect to a configured DB running on a networked machine * open query * issue a query * observe result set * disconnect your network connection (plug out and back in your cable, e.g.) * issue the query again * get meaningful error message: server closed the connection unexpectedly This probably means the server terminated abnormally before or while processing the request. In pgAdmin 1.6 RC1 (5574M): * repeat the exact same steps as above * get message ":" (just a colon) in the message window George ---------------------------(end of broadcast)--------------------------- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to majordomo@postgresql.org so that your message can get through to the mailing list cleanly |
| |||
| Shouldn't it be fairly easy to make pgAdmin reconnect do servers it has lost its connection to? After all it has all the connection information (assuming password is saved) and could try to re-establish it? I personally use a laptop and often switch connections (wired LANs, wifi, cellular broadband) and find it a major drag having to reestablish all connections: go through all the dialogs for broken connections, close and reopen all query windows (I often have about half a dozen going), making sure unsaved ones are taken care of, reopen all query files (or cut and paste from "dead" windows, etc.) Thanks! George ---------------------------(end of broadcast)--------------------------- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to majordomo@postgresql.org so that your message can get through to the mailing list cleanly |
| |||
| George Pavlov wrote: > I think Dave fixed one of the cases that caused this a few revs ago, but > another one still remains. Steps to reproduce: Actually, I didn't. Harald reported it once at the end of a very long query, but I couldn't reproduce. I think you've found the cause. > In pgAdmin 1.6 RC1 (5574M): > > * repeat the exact same steps as above > * get message ":" (just a colon) in the message window Thanks, fixed in SVN. Regards, Dave ---------------------------(end of broadcast)--------------------------- TIP 6: explain analyze is your friend |
| ||||
| George Pavlov wrote: > Shouldn't it be fairly easy to make pgAdmin reconnect do servers it has > lost its connection to? After all it has all the connection information > (assuming password is saved) and could try to re-establish it? In theory it should be easy to try to reconnect - I'll add it to the todo list. Regards, Dave ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match |