From 656f3ebfadb43355f90542e697fcc7cad975e304 Mon Sep 17 00:00:00 2001 From: Douglas J Hunley Date: Thu, 2 Apr 2026 12:34:06 -0400 Subject: [PATCH] revert: stop using conf.d directory got generated-optimizations We need to roll this change back until the other bits are updated to also use this dir or we'll keep having issues similar to inc-419 --- ansible/files/database-optimizations.service | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ansible/files/database-optimizations.service b/ansible/files/database-optimizations.service index 9f55f42c4d..f25fc09c69 100644 --- a/ansible/files/database-optimizations.service +++ b/ansible/files/database-optimizations.service @@ -4,7 +4,7 @@ Description=Postgresql optimizations [Service] Type=oneshot # we do not want failures from these commands to cause downstream service startup to fail -ExecStart=-/opt/supabase-admin-api optimize db --destination-config-file-path /etc/postgresql-custom/conf.d/generated-optimizations.conf +ExecStart=-/opt/supabase-admin-api optimize db --destination-config-file-path /etc/postgresql-custom/generated-optimizations.conf ExecStart=-/opt/supabase-admin-api optimize pgbouncer --destination-config-file-path /etc/pgbouncer-custom/generated-optimizations.ini User=adminapi