server: explore tenant routing in pg interface (also unix socket) [CRDB-14537 followup] #84585
Labels
C-enhancement
Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception)
T-multitenant
Issues owned by the multi-tenant virtual team
It is important for UX to have a single TCP port open / unix socket for all tenants running in 1 process.
The TLS client cert and/or some option in the conn URL could distinguish which tenant is being connected to.
(Alternatively, we could decide once and for all for separate interfaces. It's worth experimenting a little bit.)
Epic: CRDB-14537
Jira issue: CRDB-17748
The text was updated successfully, but these errors were encountered: