John R Pierce wrote:
> we have a fairly large database thats fed a
> constant stream of realtime data 24/7 from a factory doing both inserts
> and updates... many different sorts of things have to query this
> database, including mechanical/electrical engineering types doing adhoc
> queries for oddball reports and such who are not SQL experts. its way
> to easy for them to accidentally create a transaction that they never
> end, causing multiday blockage of VACUUM, massive table bloat, etc.
Presumably they could also run a query that accidentally consumes all
the CPU and I/O bandwidth on your server (hello missing WHERE clause!)
It sounds like what you need is an intermediate layer that enforces
transaction and query timeouts, rather than giving your mech/eng types
direct access to the DB.
-O
