RedisGreen Logo RedisGreen Changelog

RedisGreen added support for database launches in Osaka today, bringing the count of physical locations in the Asia Pacific superregion up to seven.

You can find a full list of our supported regions below, with the new region highlighted:

Region Location
af-south-1 Africa (Cape Town)
ap-east-1 Asia Pacific (Hong Kong)
ap-northeast-1 Asia Pacific (Tokyo)
ap-northeast-2 Asia Pacific (Seoul)
ap-northeast-3 Asia Pacific (Osaka)
ap-south-1 Asia Pacific (Mumbai)
ap-southeast-1 Asia Pacific (Singapore)
ap-southeast-2 Asia Pacific (Sydney)
ca-central-1 Canada (Central)
eu-central-1 Europe (Frankfurt)
eu-north-1 Europe (Stockholm)
eu-west-1 Europe (Ireland)
eu-west-2 Europe (London)
eu-west-3 Europe (Paris)
eu-south-1 Europe (Milan)
me-south-1 Middle East (Bahrain)
us-east-1 US East (N. Virginia)
us-east-2 US East (Ohio)
us-west-1 US West (N. California)
us-west-2 US West (Oregon)
sa-east-1 South America (São Paulo)

Congratulations to the core team and all of the many contributors who helped create Redis 6.2!

A few highlights:

  • LMOVE deprecates RPOPLPUSH for moving items between lists. Forgetting RPOPLPUSH will offer memory savings for our brains. docs
  • You can COPY keys of any type from one location to another. docs
  • SET will return a key’s previous value when the new GET option is used, deprecating the GETSET command. docs
  • Conditionally update scores in sorted sets using ZADD’s new LT and GT options. docs

You can read more in the release notes from the Redis core team.

Redis 6.2 is supported on the RedisGreen platform. You can build new databases using this version, or upgrade any Redis 6.0 database with no downtime.

Want to give the new release a try? Use RedisGreen to build a new Redis server now

Redis version 6.0.10 is now available. This patch release fixes and improves several operational details for Redis.

This release includes the fix from PR #8016, which ensures EXISTS no longer updates the LRU time of keys.

You can find the full release notes from the core team here

Heroku users can now attach RedisGreen servers to multiple apps or attach multiple DBs to a single app.

; heroku addons:create redisgreen:starter --as=RG_DB_0 --name rg-db-0
; cd ../another-heroku-app-dir
; heroku addons:attach rg-db-0

All common runtime and private space regions are supported.

Console screenshot showing multiple attachments

RedisMonitor also supports all Heroku Elements features.

We released a series of changes to RedisGreen’s email services over the past few days, mostly focusing on improving the clarity and consistency of communication.

Email alert latency was also substantially improved as a result of these changes, so you’re less likely to see alert emails delayed.

Redis versions 6.0.9 and 5.0.10 are now available.

These new minor versions contain bugfixes and a security patch that does not affect RedisGreen.

6.0.9 includes a new feature: CLIENT LIST now reports the memory usage of command arguments. Full release notes here

RedisGreen launched support for four new regions today, including our first in Africa and the Middle East. The highlighted regions below are now generally available, and support all RedisGreen plans at no extra charge:

Region Location
af-south-1 Africa (Cape Town)
ap-east-1 Asia Pacific (Hong Kong)
ap-northeast-1 Asia Pacific (Tokyo)
ap-northeast-2 Asia Pacific (Seoul)
ap-south-1 Asia Pacific (Mumbai)
ap-southeast-1 Asia Pacific (Singapore)
ap-southeast-2 Asia Pacific (Sydney)
ca-central-1 Canada (Central)
eu-central-1 Europe (Frankfurt)
eu-north-1 Europe (Stockholm)
eu-west-1 Europe (Ireland)
eu-west-2 Europe (London)
eu-west-3 Europe (Paris)
eu-south-1 Europe (Milan)
me-south-1 Middle East (Bahrain)
us-east-1 US East (N. Virginia)
us-east-2 US East (Ohio)
us-west-1 US West (N. California)
us-west-2 US West (Oregon)
sa-east-1 South America (São Paulo)