This would be pretty hard to put your finger on, and would depend a lot on the hosting plan you were on, server you were on and the script and/or scripts you were using and how they access your databases.  Best bet would be to go to the script creators and ask them how the script interacts with the databases as far as when somebody goes to the site, pulls up data what exactly happens.  That should give you a better idea. 

Howdy,

I am a script writer too, I mostly write php. It is very hard to hit the 50. Without getting into details, you pretty much need 50 people simultaneously requesting a page (which generates db activity) - and I assume that the scripts are single threaded (which is the case for me with PHP).

You can also reach that limit through some uncarefully planned cron jobs.

My estimate is that if your scripts are well written (and they are  ) and you hit the 50, then your site will be so popular that Google will buy it and move it to their servers while you retire to Hawaii/Bahamas/Finland/New Zealand/etc.

cheers,
wm_crash

OK, now I have more ideas. Since using PostgreSQL gives you the option to have remote connectivity, you can easily write a program to open connections in each of 50++ threads and run endless queries. I am sure that will basically raise a flag if that's what you are looking for.

I think most people are looking for ideas on how to avoid tripping on thresholds though

As a side note to anyone using PostgreSQL, you can get PostgreSQL Maestro which is good for 30 days free trial. It helped me a lot and if I find it useful enough, I may foot the $179 cost post 30 days . . . either that or will look into another GUI tool for PostgreSQL.

On the same side note, I would like to mention that I found the phpPgAdmin tool somewhere between confusing and useless . . . others may disagree.

cheers,
wm_crash