diff --git a/PgRaster.md b/PgRaster.md
index c0ea5c1..d77edd7 100644
--- a/PgRaster.md
+++ b/PgRaster.md
@@ -23,6 +23,7 @@ To check if the gdal plugin built and was installed correctly you can do:
| dbname | string | name of the database |
| user | string | username to use for connecting |
| password | string | user password to use for connecting |
+| application_name | string | connection [application_name](https://www.postgresql.org/docs/current/runtime-config-logging.html#GUC-APPLICATION-NAME). If omitted, then [fallback_application_name](https://www.postgresql.org/docs/current/libpq-connect.html#LIBPQ-CONNECT-FALLBACK-APPLICATION-NAME) = "mapnik" will be set instead.
Available in Mapnik >= 4.0 |
| table | string | name of the table to fetch, this can be a sub-query; subquery has to use syntax of: '( ) as subquery'. |
| raster_field | string | name of the raster field, in case you have more than one in a single table. Deduced from metadata tables if possible |
| raster_table | string | name of the table containing the returned raster; for determining SRIDs with subselects |
diff --git a/PostGIS.md b/PostGIS.md
index 2e507d3..ef5241a 100644
--- a/PostGIS.md
+++ b/PostGIS.md
@@ -13,6 +13,7 @@ See also a performance tuning page: [[OptimizeRenderingWithPostGIS]]
| dbname | string | name of the database |
| user | string | username to use for connecting |
| password | string | user password to use for connecting |
+| application_name | string | connection [application_name](https://www.postgresql.org/docs/current/runtime-config-logging.html#GUC-APPLICATION-NAME). If omitted, then [fallback_application_name](https://www.postgresql.org/docs/current/libpq-connect.html#LIBPQ-CONNECT-FALLBACK-APPLICATION-NAME) = "mapnik" will be set instead.
Available in Mapnik >= 4.0 |
| table | string | name of the table to fetch, this can be a sub-query; subquery has to use syntax of: '( ) as subquery'. |
| geometry_field | string | name of the geometry field, in case you have more than one in a single table. This field and the SRID will be deduced from the query in most cases, but may need to be manually specified in some cases. |
| geometry_table | string | name of the table containing the returned geometry; for determining RIDs with subselects |