Hi Jeremy,
Yes we already have statement timeout set, it just does not trigger
under extreme load cause its usually a piling of papercuts and not one
big nasty query, 26 seconds in you issue yet another query and...
boom. I guess we could prepend a custom exec that times out early and
re-sets it p
> I seem to remember it was possible to get that information out of
Rails logs pretty easily, already; and I seem recall doing that
back many years ago when I used Rails. (This is probably why
USR1 log reopening waits until a response is done before
triggering...)
Yes I am able to get the info out
Sam Saffron wrote:
> I would love to start logging the actual URL that timed out when
> murder_lazy_workers does its thing.
>
> Clearly the master process has no knowledge here, but perhaps if we
> had a named pipe from each child to master we could quickly post
> current url down the pipe so we
I would love to start logging the actual URL that timed out when
murder_lazy_workers does its thing.
Clearly the master process has no knowledge here, but perhaps if we
had a named pipe from each child to master we could quickly post
current url down the pipe so we would have something to log when
