Of course, anyone can make an error that causes a query to run
forever, just as easily as a spelling typo! :-)
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
I do not see a features suggestion list, so here goes:
I suggest Postgres get these features:
- Query times could be limited, by login id or class, so they error
out after N seconds. There could even be two thresholds, one long one
for the entire query and another, shorter one for time without
Missed it, but a quock Google summary shows that it seems to apply to admins
and so is discouraged:
_PostgreSQL: Documentation: Manuals: PostgreSQL 8.3: Client _
(http://www.postgresql.org/docs/current/static/runtime-config-client.html)
Setting statement_timeout in postgresql.conf is
