Reality check

Configuration:

one database

three tables, none more than a few thousand rows with only a few
fields per row

one, repeat one, perl cgi script on the server

4,500 users simultaneously invoking the cgi script via http requests
from remote browsers (simultaneously meaning within perhaps seconds of
each other)

Each invocation of the script opens and closes a connection to the
database, implying perhaps 4,500 ~simultaneous~ connections to the
database

The script uses a single, repeat single/unique, *postgres* user to
access the database, a user who has read and write privileges on the
tables but that's it (no table creation, etc)

In other words, there are 4,500 unique users accessing the website,
each uniquely identified via http authentication, but only ONE
postgres user who they all share to access the database, which implies
that a single, unique postgres user will be opening and closing
connections to the database perhaps a thousand times a minute.

Does this work?

If it doesn't, are there any suggestions?

Thanking you very much for time and thoughts,

John Gage

P.S. Internet users are identified within the tables in a field
containing their Apache environmental variable user name.  They cannot
collide with each other in the tables.