| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Tiger Nassau <john(dot)tigernassau(at)gmail(dot)com>, Jonathan Vanasco <postgres(at)2xlp(dot)com> |
| Cc: | PostgreSQL mailing lists <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: using postgresql for session |
| Date: | 2015-10-16 00:00:41 |
| Message-ID: | 56203E29.7010705@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Nasby | 2015-10-16 00:09:29 | Re: ID column naming convention |
| Previous Message | Tatsuo Ishii | 2015-10-15 23:05:26 | Re: pgpool ssl handshake failure |