Re: "could not reattach to shared memory" captured in buildfarm - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: "could not reattach to shared memory" captured in buildfarm
Date
Msg-id 4A000CA4.9@hagander.net
Whole thread Raw
In response to Re: "could not reattach to shared memory" captured in buildfarm  (Alvaro Herrera <alvherre@commandprompt.com>)
List pgsql-hackers
Alvaro Herrera wrote:
> Magnus Hagander wrote:
> 
>> I didn't mean race condition between backends. I meant against a
>> potential other thread started by a loaded DLL for initialization.
>> (Again, things like antivirus are known to do this, and we do see these
>> issues more often if AV is present for example)
> 
> I don't understand this.  How can memory allocated by a completely separate
> process affect what happens to a backend?  I mean, if an antivirus is running,
> surely it does not run on the backend's process?  Or does it?

Anti[something] software regularly injects code into other processes,
yes. Either by creating a thread in the process using
CreateRemoteThread() or by using techniques similar to LD_PRELOAD.

//Magnus


pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: windows shared memory error
Next
From: Chris Browne
Date:
Subject: Re: conditional dropping of columns/constraints