s to replace and instructions on where they need to go I’m
>>> happy to give it a run.
>>>
>>>
>>>
>>> Thanks!
>>>
>>>
>>>
>>> *From:* go...@googlegroups.com *On Behalf Of *Chad
>>> Wilson
>>> *Sent:*
un.
>>
>>
>>
>> Thanks!
>>
>>
>>
>> *From:* go...@googlegroups.com *On Behalf Of *Chad
>> Wilson
>> *Sent:* Wednesday, November 2, 2022 11:05 AM
>> *To:* go...@googlegroups.com
>> *Subject:* Re: [go-cd] Issues with backups o
2022 11:05 AM
> *To:* go-cd@googlegroups.com
> *Subject:* Re: [go-cd] Issues with backups on Go 22.2 and PostgreSQL v12
>
>
>
> With a bit of quick pg_dump testing on Windows (via choco install
> postgresql12/choco install postgresql14) without actually integrating
> with Go
give it a run.
Thanks!
From: go-cd@googlegroups.com On Behalf Of Chad Wilson
Sent: Wednesday, November 2, 2022 11:05 AM
To: go-cd@googlegroups.com
Subject: Re: [go-cd] Issues with backups on Go 22.2 and PostgreSQL v12
With a bit of quick pg_dump testing on Windows (via choco install
With a bit of quick pg_dump testing on Windows (via choco install
postgresql12/choco install postgresql14) without actually integrating with
GoCD) I can confirm the utility complains about the order of the positional
(non-option) dbname arguments in ways that the same utility on MacOS does
not. Onl
Technically speaking, the docs say the dbname without --dbname= should be
the last argument after all connection options, which GoCD doesn't respect.
Possibly pg_dump is more flexible on other OSes than Windows?
If you move "gocd" to the end of the command line you will probably find it
works.
If
It looks like the file version is 12.0.12.0. I'm using the version
that shipped with the PostgreSQL 12 installer. I can downgrade to a lower
PostgreSQL version if this is an issue with this release of pg_dump.
The message I get when constructing the command line using as-is from the
logs i
What version of pg_dump are you using? According to
https://www.postgresql.org/docs/current/app-pgdump.html, the command line
string looks OK. But we've not tested this on windows.
- Ketan
On Wed, Nov 2, 2022 at 4:31 AM Funkycybermonk wrote:
> Hello!
>
> New upgrade going from GoCD 20.1 to 22
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 wen
