Alter statements are considered idle for the idle timeout setting

[steven-hubbard]

Describe the problem

Please describe the issue you observed, and any steps we can take to reproduce it:

1. Set up CockroachDB cluster
2. SET CLUSTER SETTING sql.defaults.idle_in_session_timeout = '15m';
3. Issue a long running alter command
4. Connection is severed at 15m mark with below error:

ERROR: unexpected EOF
ERROR: connection lost.

unexpected EOF
Failed running "sql"

For testing we dropped the timeout to 10s and did confirm that this setting will respect a session setting for idle_in_session_timeout.

Environment:

• CockroachDB version [23.2.11]
• Server OS: Linux
• Client app: ockroach sql

Additional context What was the impact?

I can create a separate issue for this one, but it could potentially be related to server.web_session.timeout. In this case if I have the DBConsole up and am actively moving through pages or dashboards, I will be signed out regardless of how active I am once the value for web_session.timeout setting has passed.

Jira issue: CRDB-44791

[blathers-crl[bot]]

Hi @steven-hubbard, please add branch-* labels to identify which branch(es) this C-bug affects.

_{:owl: Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf.}