PostgreSQL -- bug connecting or virus generator?

[srod]

Aye, I had a false positive with the latest version of my Pyrex application with Kapersky. I then submitted the app to 20 AV programs and, again, only Kapersky complained.

Then submitted a report to Kapersky and they fixed the issue within 24 hours. I was very impressed with that turnaround.

[Lewis]

Lewis, I am also using Norton AV, and simply disconnecting the SONAR solves the problem. I know this is very irritating, because I did not have that problem with my previous AV (BitDefender).
The Sonar rings alarm because when you execute your script, it compiles to an EXE, and because this EXE suddenly appeared and is not known, Norton alerts you and destroys the temporary EXE without prompting first.
It might be an excellent scanner for normal users, but for a developer it is impossible to live with. When my Norton AV expires, I will use BitDefender again.

Aha, someone else who has experienced the same problem. Thanks for the advice, mate, I'll try it out and let everyone know what happened. I'll report this to Symantec, too -- who knows, maybe they'll want to keep me as a customer... :roll:

[charvista]

You're welcome, Lewis.
...or wanting to keep two customers

[Lewis]

You're welcome, Lewis.
...or wanting to keep two customers

Jepp, maybe two.

Ok, I went into the Norton support chat room, got a free 2010-version update (from my 2009-version purchase), and more or less solved the db-connection problem. It's now much easier to switch off the Sonar protection for a specified amount of time, say 15 minutes, while one compiles and tests an application. An acceptable solution I believe, given the need to keep oneself protected and do occasional development work.

I'm satisfied!