On 10/14/15 8:57 PM, Tiger Nassau wrote:
> maybe we will just use beaker with our bottle framework - thought it was
> duplicative to have redis since we have postgres and lookup speed should
> be trivial since session only has a couple of small fields like account
> id and role
The problem with sessions in Postgres tends to be the update rate, since
every update results in a new table tuple, and possible new index
tuples. That gets painful really fast for high-update workloads.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
