From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | "Thomas, Richard" <Richard(dot)Thomas(at)atkinsglobal(dot)com>, "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: PostgreSQL 10.20 crashes / Antivirus |
Date: | 2022-04-20 17:58:17 |
Message-ID: | ed3d5001-e00a-ad1f-2aca-5779b4785c45@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 4/20/22 10:23 AM, Thomas, Richard wrote:
> Adrian Klaver wrote:
>> On 4/20/22 01:06, Thomas, Richard wrote:
>>> The command used in a PowerShell script (run with Windows task scheduler)
>> to dump each database should evaluate to:
>>>
>>> "C:\Program Files\PostgreSQL\10\bin\pg_dump.exe" -b -v -F c -d $dbName
>>> -h localhost -p 6488 -U backup_su -f $backupFile 2`>`&1 | Out-File
>>> $pgdumpLogFile
>>
Should have asked earlier:
Have you tried doing the pg_dumps as independent actions manually for
each database instead of iterating over a list of databases in a script?
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2022-04-20 17:58:24 | Re: Unexpected result from ALTER FUNCTION— looks like a bug |
Previous Message | David G. Johnston | 2022-04-20 17:54:59 | Re: Unexpected result from ALTER FUNCTION— looks like a bug |