>Do you have a useful suggestion about how to fix it? "Stop working" is
>handwaving and merely basically saying, "one of you people should do
>something about this" is not a solution to the problem, it's not even an
>approach towards a solution to the problem.
>
>
I believe that the ability for PostgreSQL to stop accepting
queries and to log to the file or STDERR why it stopped working
and how to resolve it is appropriate.
Also it is probably appropriate to warn ahead of time...
WARNING: Only 50,000 transactions left before lock out
or something like that.
J
>---------------------------(end of broadcast)---------------------------
>TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org
>
>
--
Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC
Postgresql support, programming shared hosting and dedicated hosting.
+1-503-667-4564 - jd@commandprompt.com - http://www.commandprompt.com
PostgreSQL Replicator -- production quality replication for PostgreSQL