Postgres Pro
Downloads
Home   >   mailing lists

Re: retry shm attach for windows (WAS: Re: [HACKERS] OK, soculicidae is *still* broken) - Mailing list pgsql-hackers

From Tsunakawa, Takayuki
Subject Re: retry shm attach for windows (WAS: Re: [HACKERS] OK, soculicidae is *still* broken)
Date
Msg-id 0A3221C70F24FB45833433255569204D1F6FDC02@G01JPEXMBYT05
Whole thread Raw
In response to Re: retry shm attach for windows (WAS: Re: [HACKERS] OK, so culicidaeis *still* broken)  (Amit Kapila <amit.kapila16@gmail.com>)
Responses Re: retry shm attach for windows (WAS: Re: [HACKERS] OK, so culicidaeis *still* broken)  (Amit Kapila <amit.kapila16@gmail.com>)
List pgsql-hackers
Tree view 
From: pgsql-hackers-owner@postgresql.org
> [mailto:pgsql-hackers-owner@postgresql.org] On Behalf Of Amit Kapila
> Yes, I also share this opinion, the shm attach failures are due to
> randomization behavior, so sleep won't help much.  So, I will change the
> patch to use 100 retries unless people have other opinions.

Perhaps I'm misunderstanding, but I thought it is not known yet whether the cause of the original problem is ASLR.  I
remembersomeone referred to anti-virus software and something else.  I guessed that the reason Noah suggested 1 - 5
secondsof retry is based on the expectation that the address space might be freed by the anti-virus software.
 

Regards
Takayuki Tsunakawa

pgsql-hackers by date:

Previous
From: Petr Jelinek
Date:
Subject: Re: [HACKERS] Create subscription with `create_slot=false` andincorrect slot name
Next
From: Amit Kapila
Date:
Subject: Re: retry shm attach for windows (WAS: Re: [HACKERS] OK, so culicidaeis *still* broken)