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-21 14:46:39 |
Message-ID: | f7108b74-64e5-edfa-cfe0-cf75b1fe4854@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 4/21/22 02:13, Thomas, Richard wrote:
> Adrian (all),
>
> Thanks for your suggestions. Running the equivalent pg_dump commands at the command line instead of in a script works fine and generates no errors/warnings/McAfee messages in the Windows Event Viewer or on stdout/stderr. (Most days the backup script itself completes running multiple pg_dump without problem).
For the time being a possible solution would be to insert a time out
between iterations of:
$pgdumpCmd = "C:\Program Files\PostgreSQL\10\bin\pg_dump.exe"
$pgdumpArgs = @("-b", "-v",
"-F", "c",
"-d", $dbName,
"-h", "localhost",
"-p", "6488",
"-U", " backup_su",
"-f", $backupFile)
cmd /c $pgdumpCmd $pgdumpArgs 2`>`&1 | Out-File $pgdumpLogFile
>
> Richard
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2022-04-21 16:04:55 | Re: Huge archive log generate in Postgresql-13 |
Previous Message | Alex Aquino | 2022-04-21 13:42:10 | Re: Are stored procedures/triggers common in your industry |