Re: [HACKERS] OK, so culicidae is *still* broken - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [HACKERS] OK, so culicidae is *still* broken
Date
Msg-id 27354.1493614429@sss.pgh.pa.us
Whole thread Raw
In response to Re: [HACKERS] OK, so culicidae is *still* broken  (Amit Kapila <amit.kapila16@gmail.com>)
Responses Re: [HACKERS] OK, so culicidae is *still* broken  (Amit Kapila <amit.kapila16@gmail.com>)
List pgsql-hackers
Amit Kapila <amit.kapila16@gmail.com> writes:
> Yeah, that's right.  Today, I have spent some time to analyze how and
> where retry logic is required.  I think there are two places where we
> need this retry logic, one is if we fail to reserve the memory
> (pgwin32_ReserveSharedMemoryRegion) and second is if we fail to
> reattach (PGSharedMemoryReAttach).

I'm not following.  The point of the reserve operation is to ensure
that the reattach will work.  What makes you think we need to add more
code at that end?
        regards, tom lane



pgsql-hackers by date:

Previous
From: Amit Langote
Date:
Subject: Re: [HACKERS] Declarative partitioning - another take
Next
From: Petr Jelinek
Date:
Subject: Re: [HACKERS] snapbuild woes