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\ would be
>> excluded.
>
> I was following the instructions here:
>
> I am not particularly familiar with how our McAfee is configured or operates (all under control of our IT, including
itseems access to many of the logs). With the executable postgres.exe, they have specified that in McAfee as an
executablenot to include in "on-access scanning" (wherever the executable lives). This differs from the file read/write
scanningwhere the folders to exclude are specified. I have put in a request earlier today to add exclusions for
pg_dump.exe;maybe I'll hear back from IT in a day or so ;-(
That link also has:
"Specific issues have also been reported with McAfee and Panda
anti-virus software and NetLimiter network monitoring software. While
some people do have PostgreSQL working with these software packages,
there is no specific or even recommend solutions that have not worked in
some cases, so the issues would appear to be installation specific,
sometimes even requiring uninstallation. "
Now the last edit to the page was 2013 so not sure how relevant the
above is anymore. Also, I don't use Windows anymore(other then
occasionally working on peoples machines) so I am not the best person to
comment on current reality. Still the Postgres process seems to be
killed by an external program and my suspicion is that the AV software
is involved. Looks like this is something the Sys admins are going to
have to look into via the tools and files they have access to.
> Richard
--
Adrian Klaver
adrian.klaver@aklaver.com
