Re: Since I can't seem to unsubscribe to this mailing list, I might as well report a bug...

I can't really say whether it is a "known problem" or not, but I can tell you that keeping the SQL query window "open for the whole day" is definitely NOT A GOOD IDEA. Aside for the obvious case where someone else could possibly access your computer and do nasty things when you are not watching, there is also the possibility of power glitches and accidentally hitting the keystrokes .
So I can only caution you to do the prudent thing and only open the SQL window when you have to do transactions/queries and close it when you are done. It really doesn't take that long to open or close. Melvin Davidson
    Cell 720-320-0155

Folk Alley - All Folk - 24 Hours a day
www.folkalley.com

From: "hushthatbush(at)hushmail(dot)com" <hushthatbush(at)hushmail(dot)com>
To: "pgadmin-support(at)postgresql(dot)org" <pgadmin-support(at)postgresql(dot)org>
Sent: Wednesday, February 11, 2015 4:03 PM
Subject: [pgadmin-support] Since I can't seem to unsubscribe to this mailing list, I might as well report a bug...

When working in the SQL query window in pgAdmin, keeping it open for the whole day, I sometimes notice that it will randomly tell me that I have a syntax error somewhere in it when I run it, without having changed anything. If I just click somewhere else inside the window, such as placing the marker in the end of the query, and execute it again, it will run. So without any actual changes, it runs/doesn't run.

Is this known? Why does it happen? How can it be possible? And so on.

(No, I cannot reliably reproduce this. I don't even know when it happens. I just know it does happen, and has happened for many versions of pgAdmin over the years.)