https://blog.serviciosrogeliowar.com/en/tags/postgresql/Recent content in Postgresql on Servicios RogeliowarHugo -- gohugo.ioen© 2026 Rogelio Guerra RiverónTue, 19 May 2026 00:00:00 +0000https://blog.serviciosrogeliowar.com/en/posts/migrar-grafana-y-listmonk-a-postgresql-centralizado-en-docker/Tue, 19 May 2026 00:00:00 +0000https://blog.serviciosrogeliowar.com/en/posts/migrar-grafana-y-listmonk-a-postgresql-centralizado-en-docker/<h2 class="relative group">The initial problem <div id="the-initial-problem" class="anchor"></div> <span class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"> <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#the-initial-problem" aria-label="Anchor">#</a> </span> </h2> <p>I had Grafana and Listmonk running in Docker containers, each with its own embedded PostgreSQL instance. This worked, but it was inefficient: two database engines consuming resources and no centralized way to do backups. I decided to consolidate everything into a single shared PostgreSQL instance.</p> <h2 class="relative group">Preparation: setting up central PostgreSQL <div id="preparation-setting-up-central-postgresql" class="anchor"></div> <span class="absolute top-0 w-6 transition-opacity opacity-0 -start-6 not-prose group-hover:opacity-100 select-none"> <a class="text-primary-300 dark:text-neutral-700 !no-underline" href="#preparation-setting-up-central-postgresql" aria-label="Anchor">#</a> </span> </h2> <p>The first step was to create the PostgreSQL server that would be the central point. I did this with a dedicated docker-compose:</p>