Not our customized PostgresTimeoutTracer, but LaunchpadStatementTracer since we want this in our statement logs. We probably want two times for each statement (query time and fetch time) so we can separate the load on the db server from the load on the clients.
Not our customized PostgresTimeout Tracer, but LaunchpadStatem entTracer since we want this in our statement logs. We probably want two times for each statement (query time and fetch time) so we can separate the load on the db server from the load on the clients.