Cover debouncing of DDL queries in upgrade guide and/or FAQ

Description

Unlike driver 3, driver 4 applies debouncing to schema refreshes triggered by local DDL queries. See this mailing list discussion.

I think this is the more logical thing to do, but it would be worth pointing out in the docs, because users can get surprising results if they benchmark individual queries.

Environment

None

Pull Requests

None

Status

Assignee

Olivier Michallat

Reporter

Olivier Michallat

Labels

None

PM Priority

None

Reproduced in

None

External issue ID

None

External issue ID

None

External issue ID

None

External issue ID

None

External issue ID

None

External issue ID

None

Doc Impact

None

Reviewer

None

Size

None

Fix versions

Priority

Minor