Alvar Penning fd61f24e50 docs: PostgreSQL User for Schema Upgrades ... Explicitly state that the "icingadb" PostgreSQL database user must be used for schema upgrades. The PostgreSQL database user applying a schema upgrade is the table owner of newly create tables. When applying an Icinga DB schema upgrade not as the "icingadb" user, but as "postgres", newly created tables would not be accessible for the "icingadb" user, resulting in Icinga DB and Icinga DB Web to fail. Reported in #987.		2025-06-30 12:28:11 +02:00
..
02-Installation.md.d	GHA/docs: Containerized Setup	2025-05-27 11:25:21 +02:00
images	Docs: Account Redis' trademark policy	2024-04-11 10:07:51 +02:00
01-About.md	doc/01-About.md: Big Picture	2025-05-07 14:02:55 +02:00
02-Installation.md	Release Icinga DB Version 1.4.0	2025-06-17 12:57:56 +02:00
03-Configuration.md	doc/03-Configuration.md: Mention forced log events	2025-05-07 14:02:55 +02:00
04-Upgrading.md	docs: PostgreSQL User for Schema Upgrades	2025-06-30 12:28:11 +02:00
05-Distributed-Setups.md	Fix broken link	2025-01-08 12:58:05 +01:00
06-Migration.md	doc/06-Migration.md: ido and icingadb config sections	2025-04-25 16:36:07 +02:00
07-Operations.md	docs: Redis tuning notes for huge setups	2025-06-16 16:59:33 +02:00
icingadb-migration.example.yml	icingadb-migrate: document TLS support	2023-06-21 16:53:29 +02:00
TRADEMARKS.md	Docs: Account Redis' trademark policy	2024-04-11 10:07:51 +02:00