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 backu
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 multip
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
On 4/20/22 10:23 AM, Thomas, Richard wrote:
Adrian Klaver wrote:
On 4/20/22 01:06, Thomas, Richard wrote:
- pg_dump.exe executable is not excluded from McAfee on-access
scanning (although as recommended postgres.exe is)
Why not?
I would think the whole C:\Program Files\PostgreSQL\10\bin\ w
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
On 4/20/22 01:06, Thomas, Richard wrote:
Adrian Klaver wrote:
What are the actual commands you are using to do the above?
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
quot;localhost" (::1) and accepting
TCP/IP connections on port 6488?
Richard
-Original Message-
From: Adrian Klaver
Sent: 19 April 2022 18:11
To: Thomas, Richard ;
pgsql-general@lists.postgresql.org
Subject: Re: PostgreSQL 10.20 crashes / Antivirus
On 4/19/22 04:59, Thomas, Richard w
On 4/19/22 04:59, Thomas, Richard wrote:
A request for further suggestions for how to fix/diagnose this PG crash (having
just got back from holiday I discover that PG is still crashing even though I
have changed the pgdump target output location to a folder excluded from the
McAfee Antivirus s
A request for further suggestions for how to fix/diagnose this PG crash (having
just got back from holiday I discover that PG is still crashing even though I
have changed the pgdump target output location to a folder excluded from the
McAfee Antivirus scanning - but thanks for the suggestion Adr
On 4/6/22 07:55, Thomas, Richard wrote:
Ah... no - the AV is still allowed to run riot in the folder where the dump
file is written to. Do you think that could be the issue?
Should have added to previous post:
Try directing the pg_dump to one of the directories that have AV
scanning disabled
On 4/6/22 07:55, Thomas, Richard wrote:
Ah... no - the AV is still allowed to run riot in the folder where the dump
file is written to. Do you think that could be the issue?
I would say that would be the most likely cause. Mainly because I can
not think of another for this, "Access Denied: A
: PostgreSQL 10.20 crashes / Antivirus
On 4/6/22 03:59, Thomas, Richard wrote:
> I’ve been having problems with several PostgreSQL crashes over the
> last month (originally with 10.16, then more recently with 10.20, all
> on a Windows Server 2012R2 platform), always with a low level permissions
On 4/6/22 03:59, Thomas, Richard wrote:
I’ve been having problems with several PostgreSQL crashes over the last
month (originally with 10.16, then more recently with 10.20, all on a
Windows Server 2012R2 platform), always with a low level permissions error:
"server process (PID 5664) was termi
I've been having problems with several PostgreSQL crashes over the last month
(originally with 10.16, then more recently with 10.20, all on a Windows Server
2012R2 platform), always with a low level permissions error:
"server process (PID 5664) was terminated by exception 0xC022"
(This NT err
14 matches
Mail list logo
