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

[FR] Ability to use specific database in Redis #850

Closed
alpominth opened this issue Feb 23, 2023 · 4 comments
Closed

[FR] Ability to use specific database in Redis #850

alpominth opened this issue Feb 23, 2023 · 4 comments
Assignees

Comments

@alpominth
Copy link

Redis uses 16 databases in default Debian version.

This feature would be useful for avoiding mess up different kinds of data if the user use Redis for other than DNS caching.

@GieltjE
Copy link

GieltjE commented Oct 4, 2023

This would be really helpfull, there are too many applications about which cannot set the DB and thus all collide in DB 0.

@gthess gthess self-assigned this Oct 6, 2023
@gthess
Copy link
Member

gthess commented Oct 6, 2023

This seems trivial to do but I don't understand the usage of different DBs in redis. Is the concern only about key collisions or could you also have different configurations per DB?

@gthess
Copy link
Member

gthess commented Oct 9, 2023

It seems logical databases do not have their own configuration but they share the same options as the redis instance.
By reading this and this it seems that having dedicated instances is the better approach.
So if configuration/performance/monitoring is not a concern, as it is not solved by logical databases, the only think left is key collisions I guess?
What is a current problem that this feature would solve? :)

@GieltjE
Copy link

GieltjE commented Oct 10, 2023

For lots of smaller instances using multiple databases is just fine (we have a few servers that use it just for some unbound caching and some other small applications), running multi redis instances just add extra complexity without bringing much to the table.
For these cases it is very usefull if the databases are separated (no collisions and easier debugging/maintaince if something goes wrong with one of the applications).
As adding a database identifier shouldn't be very difficult (connection string addition if I'm correct), that would be much appreciated.

@gthess gthess closed this as completed in e98b896 Oct 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants