Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1w1J41-000Bh7-16 for pgadmin-support@arkaria.postgresql.org; Sat, 14 Mar 2026 07:05:34 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1w1J40-0017X8-0n for pgadmin-support@arkaria.postgresql.org; Sat, 14 Mar 2026 07:05:32 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1w1J3z-0017Wq-21 for pgadmin-support@lists.postgresql.org; Sat, 14 Mar 2026 07:05:32 +0000 Received: from mail-pj1-x1030.google.com ([2607:f8b0:4864:20::1030]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.98.2) (envelope-from ) id 1w1J3w-000000004ZQ-1Sna for pgadmin-support@lists.postgresql.org; Sat, 14 Mar 2026 07:05:30 +0000 Received: by mail-pj1-x1030.google.com with SMTP id 98e67ed59e1d1-35a1f3f07ebso1047699a91.3 for ; Sat, 14 Mar 2026 00:05:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enterprisedb.com; s=google; t=1773471927; x=1774076727; darn=lists.postgresql.org; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:from:to:cc:subject:date:message-id:reply-to; bh=jSi1qTsZsNECME2h1vWeZ8bR++UsN9q588soJyZZhlY=; b=k5iuObDhu5JDOhPPjkjWcgiyjtpVjDrhKZGsA4kVvrEo7r+4K+J42PYKw1fWxCNf3I pmo8RW3DM3IndjfgO5rjCWKmUNq3eWLynklzVktFvyv2+SEVpM+izglC0e4zEnuZHiiv jilODAK2NrTJquw41l/IIClTPqqzm7fvan5sSaIYWGiSEGcR7VC8ABWXSSojFdVtgJ6G ZcN+fBKq6SFrm7zigFlwhJObfVaM26I3AMarYUKG/In2PWfFqVHnJL1KxVaZ/EQ1EbK1 p+INGD5SGn3ZgsUUOU644Q1ey9+Z9hvtwwIkp+VReuSaRTHAmXbZblEy/lFzHhTC3Nwd 5pLQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20251104; t=1773471927; x=1774076727; h=references:to:cc:in-reply-to:date:subject:mime-version:message-id :from:x-gm-gg:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=jSi1qTsZsNECME2h1vWeZ8bR++UsN9q588soJyZZhlY=; b=jhN8fuw0m1gBvSr5156DS7dc2H3hCJk/OCqpRMv0t8vv4xst8UHNcgayWgp2vQOr9H NJH2pLBc5AGozpzmfXilVhEQUtR/vk73Kd1jkgPADv4rpja5BeK3VwZqLA+6H7ddMVeO uIUJ1yN8hoCF1mTFQrYTo2q0q9vfBX5chYEmo8zSA7KM2AzWe50gcscxUugKfPUOPRrk UJylJgPreM9d6deJMKY4+p1SgqqhGRdR3yZtG5J7ESyeNeAF0AMf0+V0DmXyKyCafJDv 5f4i+bX7DeG3mZOMkdYhvSDTzCFI+ahK1U4Jy8OhHv5WKQocBwSGtFMtry+eRYWTB/80 Rhmg== X-Gm-Message-State: AOJu0Yya6o3Aa27bgjaRnWH40KCnYU/xyL9wztB0mCYnW8qEa3nxljzz v/mS9btgE6LJSaBcSyLId+wg0JOx8EJOFiHTpYL69B0fiUQVbA0A/xm/OX2XnqzZoQ== X-Gm-Gg: ATEYQzzq4en2GhPvVnCOguuSZSKEbxX94JSoDjTNYeaVQkXjwdzVXp0GrpM+FJ2wvRy WAZHgB14oHL/N1tBXT+QHRMKLBHEgN1RPHWZO5FbvhJMBhrXHwpJ9l07rvmbdd5VAlePtcrdZ7L xogV/i45f2CZlCvIAWo/bgu/nXGs5/cAbCT7sGQPMe0bTzHpqsPqgAiFxIzbak52Z9Y+o0ZV6M3 sqhokqVlHjDJZPh3XftUbrveeYVLnHK/2vEA3M0iztFmc9m1SRmmBQ2yNI2Uz+fzkCx2B9k/H6Q tNV7lZyHjs+E97IJa5o5Hyg7W34iWP3BbirTNRgSpt/QeZ0vxVMRxSWtcJfWAeLimpN+vm9jvn+ l1EnINLwOPElwiN+jaCveD8GVInLqn363iyOiaNexwJEp1ZkFln9Pay/T/zk2GZ9gllBqvOK1jw 92NxNYAH+W9ixtPpylimlLmh7AmtDdkAUC/QilHbZZ1IxLRVc5N1q+G8bR7JIgsGC51Q== X-Received: by 2002:a17:90b:278d:b0:359:8d70:c4ed with SMTP id 98e67ed59e1d1-35a21e37ef6mr5887915a91.7.1773471927340; Sat, 14 Mar 2026 00:05:27 -0700 (PDT) Received: from smtpclient.apple ([163.116.213.147]) by smtp.gmail.com with ESMTPSA id 98e67ed59e1d1-359f05ee478sm14549137a91.2.2026.03.14.00.05.25 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Sat, 14 Mar 2026 00:05:27 -0700 (PDT) From: Murtuza Zabuawala Message-Id: Content-Type: multipart/alternative; boundary="Apple-Mail=_B7687B2D-D72B-4B75-A44C-D97D51A35243" Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3864.400.21\)) Subject: Re: Inquiry: Regarding creation of indivisual user on Postgre web server Date: Sat, 14 Mar 2026 12:35:14 +0530 In-Reply-To: Cc: "pgadmin-support@lists.postgresql.org" , "Jianbin YAO (EXT)" To: "Chanyel BACK (EXT)" References: X-Mailer: Apple Mail (2.3864.400.21) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --Apple-Mail=_B7687B2D-D72B-4B75-A44C-D97D51A35243 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 Hi, > 1. Under security concerns, we are trying to add individual users on = PgAdmin so that each users can access without all accessing via same = admin email. However we have realized the next morning that these = individual user data were all missing the next day. Is there a specific = setting to prevent this from happening? pgAdmin4 stores its configuration (including users) in a SQLite database = file called pgadmin4.db. Heroku has an ephemeral filesystem, and any = files written to disk disappear when it restarts. According to the = documentation, it does so every 24 hours. Heroku dynos = automatically restart = (or "cycle") at least once every 24 hours to maintain platform health = and security. This process, which may include up to 216 minutes of = random variation, cannot be disabled, requiring applications to be = designed for graceful shutdowns and stateless operation.=20 Key Aspects of Daily Dyno Restarts: Purpose: Ensures app health and shifts applications to new physical = hardware if necessary. Timing: Roughly every 24 hours, plus a random delay to prevent all dynos = in an app from restarting simultaneously. Manual Restarts: Running heroku restart manually resets the 24-hour = timer. Impact: Any changes made to the local ephemeral filesystem are deleted = upon restart. Exceptions: While rare, some specialized private spaces may have = different configurations, but standard cycling is a core platform = feature.=20 Heroku Dev Center +2 Solution - You need to store the pgAdmin data directory typical location = /var/lib/pgadmin outside the ephemeral filesystem. > 2. Due to the same security issue, we would like to track logs for = which user actions. With the condition that individual user accounts are = created permanently, are there a way to check user actions in PgAdmin? = We would also like to know what can be tracked(login info, sql execution = on tables, etc) and if so, how to track them.=20 This must be done in PostgreSQL, not pgAdmin (it is just a client) Thank you! Murtuza Zabuawala enterprisedb.com > On 12 Mar 2026, at 2:26=E2=80=AFPM, Chanyel BACK (EXT) = wrote: >=20 > To add on regarding the first question, we are running pgAdmin on = Heroku. > Theefore We tried adding the following Config Vars on Heroku side to = maintain user accounts. However, all created user accounts on PgAdmin = side were deleted again. >=20 > Could you help us identify the problem? We have conducted as = instructed by the Heroku side, but did not work. We were instructed to = consult with the PgAdmin side. >=20 > >=20 > >=20 > Your immediate response would be greatly appreciated. >=20 > Chanyel Back > =20 > From: Chanyel BACK (EXT) > Sent: Wednesday, March 11, 2026 10:55 AM > To: pgadmin-support@lists.postgresql.org > Cc: Jianbin YAO (EXT) > Subject: Inquiry: Regarding creation of indivisual user on Postgre web = server > =20 > Hello Postgre Support Team, > =20 > Thank you always for your support. > Regarding the inquire mentioned on the tile we would like to ask two = main questions. > For your information, we are currently using the browser version of = PgAdmin, connected to the app in Heroku. >=20 > 1. Under security concerns, we are trying to add individual users on = PgAdmin so that each users can access without all accessing via same = admin email. However we have realized the next morning that these = individual user data were all missing the next day. Is there a specific = setting to prevent this from happening? >=20 > 2. Due to the same security issue, we would like to track logs for = which user actions. With the condition that individual user accounts are = created permanently, are there a way to check user actions in PgAdmin? = We would also like to know what can be tracked(login info, sql execution = on tables, etc) and if so, how to track them.=20 >=20 > Thank you for your support in advance. >=20 > Chanyel Back --Apple-Mail=_B7687B2D-D72B-4B75-A44C-D97D51A35243 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=utf-8 Hi,

1. Under security concerns, = we are trying to add individual users on PgAdmin so that each users can = access without all accessing via same admin email. However we have = realized the next morning that these individual user data were all = missing the next day. Is there a specific setting to prevent this from = happening?


pgAdmin4 stores its configuration (including users) in a SQLite = database file called pgadmin4.db. Heroku has an ephemeral filesystem, and any files written to disk disappear when it restarts. According to the documentation, it = does so every 24 hours.


Heroku dynos automatically restart (or "cycle") at = least once every 24 hours to maintain platform health and security. = This process, which may include up to 216 minutes of random variation, = cannot be disabled, requiring applications to be designed for graceful = shutdowns and stateless operation. 
Key Aspects of Daily Dyno = Restarts:
  • Purpose: Ensures app health and = shifts applications to new physical hardware if = necessary.
  • Timing: Roughly every 24 hours, plus = a random delay to prevent all dynos in an app from restarting = simultaneously.
  • Manual = Restarts: Running heroku = restart manually resets the 24-hour = timer.
  • Impact: Any changes made to the = local ephemeral filesystem are deleted upon = restart.
  • Exceptions: While = rare, some specialized private spaces may have different configurations, = but standard cycling is a core platform feature. 
    • Solution - You need to store the pgAdmin data directory typical location /var/lib/pgadmin outside the ephemeral filesystem.


2. Due to the same security issue, we would like to track = logs for which user actions. With the condition that individual user = accounts are created permanently, are there a way to check user actions = in PgAdmin? We would also like to know what can be tracked(login info, = sql execution on tables, etc) and if so, how to track = them. 

This must be done in PostgreSQL, not pgAdmin (it is just a = client)


Thank you!

Murtuza = Zabuawala


On 12 Mar 2026, at 2:26=E2=80=AFPM= , Chanyel BACK (EXT) <chanyel.back@chanel.com> wrote:

To add on regarding the first = question, we are running pgAdmin on Heroku.
Theefore We tried adding = the following Config Vars on Heroku side to maintain user accounts. = However, all created user accounts on PgAdmin side were deleted = again.

Could you help us identify the problem? We have conducted = as instructed by the Heroku side, but did not work. We were instructed = to consult with the PgAdmin side.

<image001.png>

<image002.png>

Your immediate response would be greatly = appreciated.

Chanyel Back
 
From: Chanyel BACK = (EXT)
Sent: Wednesday, March 11, 2026 = 10:55 AM
To: pgadmin-support@lists.postgre= sql.org
Cc: Jianbin YAO (EXT) = <jianbin.yao@chanel.com>
Subject: Inquiry: Regarding creation = of indivisual user on Postgre web = server
 
Hello Postgre Support Team,
 
Thank you always for your = support.
Regarding = the inquire mentioned on the tile we would like to ask two main = questions.
For your = information, we are currently using the browser version of PgAdmin, = connected to the app in Heroku.

1. Under security concerns, we = are trying to add individual users on PgAdmin so that each users can = access without all accessing via same admin email. However we have = realized the next morning that these individual user data were all = missing the next day. Is there a specific setting to prevent this from = happening?

2. Due to the same security issue, we would like to = track logs for which user actions. With the condition that individual = user accounts are created permanently, are there a way to check user = actions in PgAdmin? We would also like to know what can be tracked(login = info, sql execution on tables, etc) and if so, how to track them. 

Thank you for your = support in advance.

Chanyel = Back

= --Apple-Mail=_B7687B2D-D72B-4B75-A44C-D97D51A35243--