Good Day

Firstly I apologise if this has been formally requested before or if there is a 
better place for this to go..

While trying to debug why the docker image would not deploy and run on Azure 
Kubernetes Service (AKS) I finally got to the bottom of it in that AzureFile 
and possible also AzureDisk storage backends have issues with SQLITE and 
locking (https://github.com/kubernetes/kubernetes/issues/59755) - while I was 
able to workaround the issue with the nobrl mount option mentioned on the 
linked issue it does raise concerns about potential data corruption of the 
SQLite DB in event of any issues. At least as it concerns to AKS there isn't 
any real immediate improvement to be had.

It got me thinking, it would be really great if pgadmin could support 
alternative storage backends for this data, my first prize would obviously be 
towards supporting postgres as a backend.

While I appreciate there aren't particularly any performance concerns with 
sqlite as its used in pgadmin4 it but it does potentially cause challenges 
when/if you need to scale the deployment and how you manage things at that 
point. It really would make life easier from a management perspective once you 
need to start scaling to multiple instances of pgadmin or want to create DR 
scenarios and replicatio of the data if other backends were available.

Anthony Somerset


This email disclaimer applies to the original email, all attachments and any 
subsequent emails sent by Liquid Telecom. This email contains valuable business 
information that is privileged, confidential and/or otherwise protected from 
disclosure, intended only for the named person or entity to which it is 
addressed. If you are not the intended recipient of this email and you received 
this e-mail in error, any review, use, dissemination, distribution, printing or 
copying of this e-mail is strictly prohibited and may be unlawful and/or an 
infringement of copyright. Please notify us immediately of the error and 
permanently delete the email from your system, retaining no copies in any 
media. No employee or agent is authorized to conclude any binding agreement on 
behalf of Liquid Telecom with another party or give any warranty by email 
without the express written confirmation by an authorized representative or a 
director of Liquid Telecom. Nothing in this email shall be construed as a 
legally binding agreement or warranty or an offer to contract. Liquid Telecom 
will not be responsible for any damages suffered by the recipient as a result 
of the recipient not taking cognizance of this principle. Liquid Telecom 
accepts no liability of whatever nature for any loss, liability, damage or 
expense resulting directly or indirectly from the access of any files which are 
attached to this message. Any email addressed to Liquid Telecom shall only be 
deemed to have been received once receipt is confirmed by Liquid Telecom orally 
or in writing. An automated acknowledgment of receipt will not suffice as proof 
of receipt by the Liquid Telecom. This email disclaimer shall be governed by 
the laws of South Africa.

Reply via email to