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 <https://www.google.com/goto?url=CAESbwE7q4ylbV_Z7e4iF417CNdK8GZ0fmM5dXsc6NI1oqfZJI3rJS3vztI9fjh1wvCw8XrdCIM4pIzzqvijzNLQABc4R2wh3VATq0Fs0WxCRZUxbeFRa-NI-1wuv1GONJn-VLqn9nDZfIjjHR_BLFCrxA==> 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. 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. This must be done in PostgreSQL, not pgAdmin (it is just a client) Thank you! Murtuza Zabuawala enterprisedb.com <http://enterprisedb.com/> > On 12 Mar 2026, at 2:26 PM, Chanyel BACK (EXT) <[email protected]> > 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: [email protected] > Cc: Jianbin YAO (EXT) <[email protected]> > 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
