[02:46] Evening [02:53] <_stink_> yo [14:15] good morning! [14:23] good morning! [14:24] How's the morning? [14:45] * rick_h_ grumbled [15:00] That good eh? [15:14] well, sitting on an ice pack post-surgery yay [15:17] WHAT? you got surgered? [15:18] yea, well I guess 'inpatience procedure' might be the right word? [15:27] oh no. its surgery! [15:27] That is an old bit from city slickers. [15:27] about aging. [15:27] "40s, you grow a little pot belly, you grow another chin. The music gets too loud" [15:27] "An old girlfriend from high school becomes a grandmother" [15:28] "50s, you have a minor surgery. You'll call it a procedure, but it's a surgery" [15:28] "60s, you'll have a major surgery The music is still loud" [15:28] "but you can't hear it anyway" [15:28] " 70s, you and the wife retire to Fort Lauderdale" [15:28] "You eat dinner at two in the afternoon" [15:28] I always liked that bit :) [15:28] heal quickly, rick_h_ ! [16:00] :\ [16:06] rick_h_: Hope the in-patient procedure doesn't become impatience [16:46] Can someone give me a link with compelling reasons for using MongoDB over PostgreSQL? [16:46] cmaloney: no [16:47] absolutely not [16:47] cmaloney: never [16:47] rick_h_: I know. Apparently I have to find the devil's advocate [16:47] cmaloney: I am the devil's advocate [16:47] heh [16:47] we run all of juju, plus a handful of production services on mongodb [16:47] and we wish we had the chance to port them all, including juju, to pgsql [16:47] the end [16:47] cmaloney: there is never a good reson to use mongodb [16:48] cmaloney: masochism maybe? [16:48] cmaloney: we've got thousands and thousands of lines of code that say "mongodb is always a mistake" from CMS type apps, distributed apps, small scale,larger scale [16:49] rick_h_: Yeah, I know. MongoDB is terrible. [16:49] cmaloney: I'll play - scale out is easier. [16:49] We ran it at SF. It was great when it worked, and terrible when it sort of worked. [16:50] cmaloney: mongodb shards are more transparent. with postgrsql you have to think more aobut your sharding and scale out story. your app probbaly needs to know about it. with mongodb its transparent [16:50] jrwren: except things like replicasets and split brain is too easy to hit, etc [16:50] cmaloney: the protocol awareness of master and slave replicasets is nice because client APIs can automatically retry on a different member of the replicaset [16:50] So hstore over mogodb then? [16:50] rick_h_: shush, I'm playing devils advocate. [16:50] cmaloney: every single time [16:51] rick_h_: i'd still NEVER use mongodb. I'm just giving cmaloney what he asked for. [16:51] cmaloney: especially because you can mix the right data into hstore and keep the right tool for the job for non-key/value stuff [16:51] Honestly the sharding is pretty much the only reason I can think of [16:51] cmaloney: jsonb FTW [16:51] but we're never going to be using it [16:54] Thanks, though. I knew Juju was running MongoDB (Allura ran it as well. Not sure if they still are or not) [16:55] and I knew I could count on rick_h_ for the vitriol if it wasn't working out. [16:55] and jrwren for the technical reasons why it might be useful. [16:55] cmaloney: it's not even vitriol, just real world experience sinking in hundreds of dev hours per day into it [16:55] Well, vitriol in that it isn't working out [16:55] cmaloney: how do you do incremental mongodb backups? [16:55] trick question! you don't! [16:56] jrwren: Heh [16:56] Not sure how to do incremental SQL backups, honestly [16:56] outside of timestamp-based transactions [16:56] or replication [16:57] most rdbms suport them. [16:57] postgresql supports transaction log reply for point in time recovery [16:57] *replay* [16:57] Right [16:57] I don't think of that as incremental though [16:57] but it is. [16:57] though my understanding is based on "dump" [16:57] you do a single full backup and incrementally backup the transaction logs [16:57] Right [16:58] That would qualify then [16:58] Most of our backups are essentially "dump" [17:00] do you really take fs dump? [17:00] not tar or rsync? [17:00] I think we're using backuppc or something similar [17:00] not that close to the hardware [17:00] iirc that just fronts rsync or tar. [17:00] Yeah, it wouldn't surprise me [17:10] I think finding an article that says MongoDB is a better fit than PostgreSQL is like trying to find a unicorn in my underpants [18:12] jrwren: Chazzano in Ferndale is super quick about shipping coffee FYI. I ordered Sunday, arrived today [18:15] cscheib: COOL! [18:15] so... next LTS, Xenial is not getting http2 support for "security reasons" but I've not seen those reasons documented :( [18:15] https://bugs.launchpad.net/ubuntu-release-notes/+bug/1503051 [18:22] So will it be eventually released when those bugs are fixed? [18:22] I was running out of coffee, was afraid it wasn't going to arrive in time [18:23] cscheib: That sounds about right [18:23] since mon would be pick-up, and mon-tue would be sorting and what-not [18:23] <- the usps whisperer [18:23] not a particular fan of said governmental entity :P [18:24] but, they did me good, this time [18:24] I prefer the USPS by a country mile [18:25] USPS > UPS > FedEx / DHL / * [18:25] at least for shipping [18:25] cmaloney: i've seen no evidence that it will get into LTS 16.04. So maybe 18.04 :( [18:25] UPS I prefer for delivery because they show up around noon [18:25] UPS treats me well [18:25] jrwren: That's kind of silly [18:25] very very well [18:26] cscheib: I'm intrigued [18:27] Although I just got notification of something arriving at Allen Park that was electronically requested on Dec 2nd [18:27] At least USPS has been good about any cock-ups they've done [18:27] as opposed to FedEx which still hasn't updated what happened to a package that went missing in October. [18:28] Seriously, this is some CNN-level-Malaysian-flight-into-black-hole mystery here [18:28] UPS has mychoice, I can see when seller ships package, estimated time frame of delivery (sometimes), date of delivery, when it's been delivered [18:28] all without having to type in a tracking number [18:28] my.usps.com [18:28] Same thing [18:29] and free. ;) [18:29] but this is automated and free and emails me without any work :P [18:29] I've never found USPS's tracking to be at all useful [18:29] This is automated, and free, and emails me without any work [18:29] it's gotten better [18:29] "it'll arrive some tiem this week" [18:29] granted there's a few times where stuff has "transported" [18:29] but it's quite good [18:30] About 90% of where UPS's tracking is [18:30] the worst is when Amazon uses SmartPost or whatever to ship something [18:30] They all do [18:30] that "last mile" takes forever [18:30] Last mile is USPS because it's cheaper [18:30] yup [18:31] Which keeps my boyfriend-in-law with a decent job [18:31] (he's a postal carrier) [18:31] amazon drones are gonna RULE!!! [18:32] I have never heard the phrase boyfriend-in-law, heh [18:32] Well, it's my sister-in-law's boyfriend [18:32] ergo... [18:32] he's cool, so that's where he gets "boyfriend-in-law" [18:34] <_stink_> i feel like there has to be a moment where you tell him you now consider him your boyfriend-in-law [18:35] oooh, this Ethiopia Harrar smells sooo good. [18:37] _stink_: heh [18:37] I think I've said as much in front of him [18:37] <_stink_> awww. [18:44] it's a bromance [18:45] Kindly never use that word around me ever again [18:45] amen [18:48] * cscheib files away in the "buttons to push" file [18:51] coffee be good. wise purchase.