On 1/3/2016 1:32 PM, Melvin Davidson wrote:
As others have pointed out, storing session data in a table is not a good idea. Even if you use TRUNCATE, you will still not reclaim all the space used unless you use vacuum full. More to the point, if you absolutely must store session data, then why not just do it in a TEMPORARY table, which will reside in memory and clean itself up when the session ends?
The fundamental problem is that HTTP itself is stateless, and user sessions have to be enforced by the web app, with the aid of browser cookies. you can't simply directly link a http connection to a SQL connection and assume thats a session.
-- john r pierce, recycling bits in santa cruz -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
