diff --git a/docs/30_Configuration/60_File_env.md b/docs/30_Configuration/60_File_env.md
index 55f7dbf0a3d9f956672fecccce003401c66fc8f7..2fceb9299bc2859fa10f71132b33ad1377b0fc6e 100644
--- a/docs/30_Configuration/60_File_env.md
+++ b/docs/30_Configuration/60_File_env.md
@@ -60,6 +60,19 @@ RESTIC_PARAMS=--no-scan
 
 You can override used parameters during backup. The parameters for mysqldump are in env_defaults. If you want to change them then put ``LD_MYSQL_DUMP_PARAMS=...`` into env file.
 
+### Localdump :: Pgsql
+
+Postgres backup supports backups with a snapshot database using `CREATE DATABASE snapshot_<SCHEMA> WITH TEMPLATE <SCHEMA>`.
+The backup script detects if a server is writable or readonly (slave). On a writable system the snapshot creation is activated.
+
+The creation of a snapshot database fails if a user is connected on the origin database. It is posible to disconnect all users but shouldn't be triggered during production times. You can configure a night time when to allow the disconnect (default: no disconnect).
+
+You can put these variables into env:
+
+* LD_PGSQL_SNAPSHOTS=0 - disable snapshot on a writable database server
+* LD_PGSQL_DISCONNECT_BEFORE - time in the morning until to allow disconnect; eg. "03:00"
+* LD_PGSQL_DISCONNECT_AFTER - time in the night when to allow disconnect; eg "22:00"
+
 ### Transfer :: Restic
 
 There are some environment variables for tuning