Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

server: explore tenant routing in pg interface (also unix socket) [CRDB-14537 followup] #84585

Closed
Tracked by #91282
knz opened this issue Jul 18, 2022 · 1 comment · Fixed by #92580
Closed
Tracked by #91282
Assignees
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

Comments

@knz
Copy link
Contributor

knz commented Jul 18, 2022

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

@knz knz added the C-enhancement Solution expected to add code/behavior + preserve backward-compat (pg compat issues are exception) label Jul 18, 2022
@knz
Copy link
Contributor Author

knz commented Jul 18, 2022

NB: we might need a variant of this to implement the pivot migration in INI-215.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Projects
None yet
1 participant