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

From: Ashesh Vashi <ashesh(dot)vashi(at)enterprisedb(dot)com>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: Dave Page <dpage(at)pgadmin(dot)org>, pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org>, Murtuza Zabuawala <murtuza(dot)zabuawala(at)enterprisedb(dot)com>
Subject: Re: Server side session management using the SQLite (per session) database
Date: 2016-03-23 09:08:20
Message-ID: CAG7mmoyyx4gjK-75J6tnQx2xx_axuthegx3gXqQE7u0nD+YQfA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

On Wed, Mar 23, 2016 at 2:34 PM, Magnus Hagander <magnus(at)hagander(dot)net>
wrote:

>
>
> On Tue, Mar 22, 2016 at 4:11 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.
>>
>> I assume it's expected at this point that new connections still fail if
>> the backend is restarted (that would come with graceful reconnections)?
>>
>>
>
>
> Heh, does this actually make sqlite a dependency for pgadmin4? That's kind
> of hilarious :)
>
:)

We're already using sqlite for saving the local configurations instead of
flat file, which caused a lot of problem in past with pgAdmin 3.

>
> Not saying it's wrong, absolutely not. Just expect a few laughs coming off
> that one :D
>

Do not have time to implement another database. :P

--

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>

>
>
> --
> Magnus Hagander
> Me: http://www.hagander.net/
> Work: http://www.redpill-linpro.com/
>

In response to

Browse pgadmin-hackers by date

  From Date Subject
Next Message Dave Page 2016-03-23 09:15:06 Re: Server side session management using the SQLite (per session) database
Previous Message Magnus Hagander 2016-03-23 09:04:23 Re: Server side session management using the SQLite (per session) database