Re: Server side session management using the SQLite (per session) database

Hi

On Thu, Mar 17, 2016 at 5:46 PM, Ashesh Vashi <ashesh(dot)vashi(at)enterprisedb(dot)com
> wrote:

> Hi Dave/team,
>
> As discussed, I have implemented the server side session management using
> the SQLite database.
>
> Implementation:
> * It creates/reuses the sqlite database per session.
> * Stores the key (as text)/value (as blob) in the sqlite database.
> * Needs to provide the session directory, where you want to store those
> sessions. If this directory does not exist, it creates the directory with
> 700 permission. (Default: <USER_HOME>/.pgadmin/sessions directory.)
> * Also - sets default value for the log file to be stored in the
> '<USER_HOME>/.pgadmin' directory. This will allow us to keep separate
> configuration per user on any operation system, when running through
> runtime.
>
> This implementation uses sqlite as session storage, it may affect because
> of explicit file system I/O operation. Though - performance should not be a
> big issue, as we're not targeting to support very huge parallel sessions.
>

Thanks - applied.

I assume it's expected at this point that new connections still fail if the
backend is restarted (that would come with graceful reconnections)?

> Murtuza,
>
> I have tested it on Python 2.7.
> Can you please take a look at it, and do the needful to make it work on
> Python 3.x?
>

Please double-check Windows as well.

Thanks.

--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company