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

From: Ashesh Vashi <ashesh(dot)vashi(at)enterprisedb(dot)com>
To: Neel Patel <neel(dot)patel(at)enterprisedb(dot)com>, Murtuza Zabuawala <murtuza(dot)zabuawala(at)enterprisedb(dot)com>
Cc: pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org>, Dave Page <dpage(at)pgadmin(dot)org>
Subject: Re: Server side session management using the SQLite (per session) database
Date: 2016-03-23 07:32:41
Message-ID: CAG7mmoybh1S+3-_J4GHK=y2g6xYZ0zEvjQxaC6pREJDXfgWf=g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

On Tue, Mar 22, 2016 at 8:41 PM, Dave Page <dpage(at)pgadmin(dot)org> wrote:

> 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.
>
Thanks.

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

Do you mean to say?
- New Connection to the server should not be established (if it was
restarted).
- What about the existing connection, should it re-establish the connection
after the backend restart (when allowed)?

--

Thanks & Regards,

Ashesh Vashi
EnterpriseDB INDIA: Enterprise PostgreSQL Company
<http://www.enterprisedb.com/>

*http://www.linkedin.com/in/asheshvashi*
<http://www.linkedin.com/in/asheshvashi>

>
>
>> 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 - Murtuza for the python 3 support patch.

Neel - can you please take a look at the Windows?

--

Thanks & Regards,

Ashesh Vashi
EnterpriseDB INDIA: Enterprise PostgreSQL Company
<http://www.enterprisedb.com/>

*http://www.linkedin.com/in/asheshvashi*
<http://www.linkedin.com/in/asheshvashi>

>
> Thanks.
>
> --
> Dave Page
> Blog: http://pgsnake.blogspot.com
> Twitter: @pgsnake
>
> EnterpriseDB UK: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
>

In response to

Responses

Browse pgadmin-hackers by date

  From Date Subject
Next Message Neel Patel 2016-03-23 08:34:07 Re: Server side session management using the SQLite (per session) database
Previous Message Khushboo Vashi 2016-03-23 07:27:07 Re: pgAdmin4 PATCH: Domain Module