Method logQueryFinished

server/conn.go:478–491

logQueryFinished records a query terminating on the worker. Counter- part to logQueryStarted; emit once per query regardless of outcome so the start/finish pair is always balanced. On error paths logQueryError still fires for severity routing (Info vs Error based on SQLSTATE class). logQueryFinishe

(query string, start time.Time, rows int64, err error)

func (c *clientConn) queryContextForCursor() (context.Context, func()) {
	return c.queryContextInner(false)
}

func (c *clientConn) queryContextInner(monitor bool) (context.Context, func()) {
	c.ensureConnectionContext()
	// Registering for cancellation is the moment the statement becomes live to
	// the client, which makes this the one place every execution path — simple,
	// batched, extended, COPY, cursor — passes through on its way to an engine.
	// The QueryStart event and the ExceptionBeforeStart boundary both hang off
	// it rather than off a call added to each path.
	c.markExecStarted()
	// Carry the statement's ID to the engine. The worker stamps it on its own
	// logs, so a client complaint can be followed from this connection into the
	// pod that ran the statement.
	ctx, cancel := context.WithCancel(wire.WithQueryID(c.ctx, c.currentQueryID()))
	key := c.backendKey()
	c.server.RegisterQuery(key, cancel)