If your r/w workload is bigger than shared_buffers, seriously consider enabling backend_flush_after. Both throughput *and* jitter are considerably better with it enabled.pic.twitter.com/PYDSemn5Dg
You can add location information to your Tweets, such as your city or precise location, from the web and via third-party applications. You always have the option to delete your Tweet location history. Learn more
I think it's still possible to find cases where it regresses workloads. In particular workloads where the hot data set is below a gigabyte or three, but still bigger than shared buffers. Which probably isn't that uncommon, unfortunately.
Regressions in that kind of scenario IIRC are behind that warning, and why it's not enabled by default (even though it was for a while, shortly after the patch got in).
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.