K
KWSMaster
Guest
It would be kind of nice if we could specify a -maxL or something similar to apply a per-user limit ot the number of locks that can be taken by a user's ABL session. We have had a runaway user transaction cause a 100K lock table overflow when absolutely no process a user should run should ever exceed 20K. The only processes that we ever want to have access to the full lock table is background tasks. I would be fully accepting of a user throwing a lock table overflow with all the penalties if that user hit the configured max for their session. I know all the developers are going to jump in here with you should never write code that can do that but it happens in a rapidly changing environment, especially with a lot of new developers learning database techniques.
Continue reading...
Continue reading...