dustin
/
configpolicy
1
1
Fork 0
Code Issues Releases Activity

r/postgres-exporter: Do not connect to tempate1 DB 

It turns out, having the exporter connect to the _template1_ database is
not a great idea.  PostgreSQL does not allow creating a new database if
the template database is currently being accessed by any clients.  Since
_template1_ is the default choice, the `createdb` command will probably
fail.

It doesn't specifically matter which database the exporter connects to,
since it reads most (all?) of its data from the PostgreSQL catalog,
which isn't database-specific.
frigate-exporter
Dustin 2024-09-02 21:15:23 -05:00
parent a0378feda8
commit 6f9cd7e4af
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
roles/postgres-exporter/templates/postgres-exporter.container.j2
View File

@ -6,7 +6,7 @@ After=postgresql.service
[Container]
Image=quay.io/prometheuscommunity/postgres-exporter:v0.15.0
Environment=DATA_SOURCE_URI='postgres-exporter@:5432/template1?host=/run/postgresql'
Environment=DATA_SOURCE_URI='postgres-exporter@:5432/postgres?host=/run/postgresql'
Mount=type=bind,source=/run/postgresql,target=/run/postgresql
# container_t cannot access the PostgreSQL socket postgresql_var_run_t
SecurityLabelDisable=true