10:20:53 GMT <King_DuckZ> hey all
10:21:44 GMT <King_DuckZ> it's so quiet today on irc... I'm trying to brag about the progress I've done in http://github.com/KingDuckZ/tawashi but nobody seems to be around
10:21:57 GMT <King_DuckZ> I've made*
10:32:17 GMT <colo-work> King_DuckZ, still, I'd like to congratulate you :)
10:32:22 GMT <colo-work> and please keep up the good work
10:51:39 GMT <King_DuckZ> colo-work: lol thank... I guess :D
10:52:11 GMT <King_DuckZ> if you try it and have suggestions or feedback, I'm very interested in hearing back
10:53:30 GMT <King_DuckZ> I know I'll get rid of all the to-and-fro communication with redis by offloading work to a lua script, that's not going to happen soon but it's an improvement I have in mind already... there surely are others I didn't think of yet, tho
13:15:23 GMT <nowashburn> hello, I've been messing around with  Keyspace Notifications, specifially on SET commands on a small amount of data and only a few subscribers. Everything is going great so far. However, im wondering if anyone has experience with  Keyspace Notifications and replication?
13:20:11 GMT <minus> i think it works on slaves too, but that's trivial to try anyway: redis-server --slave-of '127.0.0.0 6379' --port 6380 --save ''
13:20:19 GMT <minus> ^ nowashburn
13:23:42 GMT <nowashburn> minus, thanks. I guess im just moreso wondering about timing. like suppose I have three servers (one master + two slaves) and and handful of apps listening for changes on a particular key, then getting the updated value, some from the slaves. would redis ensure that the slaves have been updated before broadcasting the update message?
13:24:53 GMT <minus> pretty sure it does keep the order
13:25:40 GMT <minus> it might even be possible that you have to explicitly enable keyspace notifications on the slave and that the slave instance then handles the notifications independently from replication
13:26:34 GMT <nowashburn> i see, very good point. thanks again
16:08:22 GMT <catbeard> so if i have PHP configured to use redis for sessions, how would i grab info on current sessions from an IP
16:11:04 GMT <catbeard> or would i have to know the namespace and variable for the app that records it beforehand i guess?
16:18:01 GMT <minus> catbeard: you'd probably have to know the session id. if the session data contains the ip you could scan over all sessions and look for that
16:18:56 GMT <catbeard> is there some redis-fu for key scanning with regex?
16:19:31 GMT <catbeard> and how a php session might be formatted as a key
16:19:36 GMT <minus> KEYS supports wildcards
16:19:48 GMT <minus> SCAN if you don't want everything at once
16:19:56 GMT <minus> see the website for more details
16:20:21 GMT <minus> you can use those commands from redis-cli
16:24:06 GMT <catbeard> cool
18:39:30 GMT <jordanl> i'm considering redis to store a set of semi-static data. by semi-static i mean a new version of the dataset would be uploaded infrequently (monthly, for us).
18:39:58 GMT <jordanl> does redis provide any features to make it easy to separate or namespace each version of the data set, then allow an old version to be deleted easily?
18:41:16 GMT <minus> you can use different databases for that and wipe those individually
18:41:26 GMT <minus> and from 4.0 on you can even swap them
18:41:57 GMT <jordanl> thanks
18:42:12 GMT <jordanl> i just found this command in the docs https://redis.io/commands/flushdb
18:47:07 GMT <jordanl> does redis have a limit to the number of databases you can use?
18:47:10 GMT <jordanl> i can't find it in the docs
18:47:31 GMT <jordanl> i see they're referenced by an integer ID
18:47:51 GMT <minus> yes, the limit is configured in the config