Hello!
New upgrade going from GoCD 20.1 to 22.2 and migrated to PostgreSQL v12 on
Windows. Everything is now working properly but the backups were blowing up
due to not being able to find pg_dump. I added the bin for PostgreSQL to
the system path and the backup exits with a status code 1. I went back and
checked the command and it looks like it might be blowing up because the
dbname isn't defined with a parameter name.
The executing bit is showing [pg_dump, --no-password, --host=localhost,
--port=5432, --username=<removed>, gocd, --file=C:\Program Files (x86)\Go
Server\artifacts\serverBackups\backup_20221101-215455\db.gocd] with
environment {PGPASSWORD=<removed>}
The gocd bit in the middle appears to be the dbname but its not qualified
as --dbname. Is that a bug or is there something I haven't configured
properly? If I take that parameter string and run it in a command prompt
with the commas removed it blows up on the parameters not matching up.
Adding the --dbname= to that parameter works for me but I'm not sure if
that should be required.
I can roll back to H2 but I was hoping there would be a performance
improvement and future-proofing if I went ahead with the migration now. If
that doesn't make sense then I'm happy to stay with H2.
Thanks!
--
You received this message because you are subscribed to the Google Groups
"go-cd" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/go-cd/1a7de3d6-8dae-4da0-b675-6d02ab885993n%40googlegroups.com.
