Re: Dynamic Shared Memory stuff

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Cc: Noah Misch <noah(at)leadboat(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Dynamic Shared Memory stuff
Date: 2014-04-16 16:08:44
Message-ID: CA+TgmoYf=cza6ik0H6evY6cVqHaOJwaHa_R_pZ+vphxcc7OfVQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Apr 15, 2014 at 10:46 PM, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
> On Wed, Apr 16, 2014 at 3:01 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>> On Tue, Apr 15, 2014 at 12:33 AM, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
>>> On Mon, Apr 14, 2014 at 10:03 PM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>>>> For the create case, I'm wondering if we should put the block that
>>>> tests for !hmap *before* the _dosmaperr() and check for EEXIST. What
>>>> is your opinion?
>>>
>>> Either way is okay, but I think the way you are suggesting is better as it
>>> will make code consistent with other place (PGSharedMemoryCreate()).
>>
>> OK, can you prepare a patch?
>
> Please find attached patch to address this issue.
> One minor point to note is that now we have to call GetLastError() twice,
> once inside error path and once to check EEXIST, but I think that is okay
> as existing code in PGSharedMemoryCreate() does it that way.

OK. I committed this blindly, but I don't have a Windows dev
environment, so please keep an eye on the Windows buildfarm members
and provide follow-on patches if any of them get unhappy about this.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Hannu Krosing 2014-04-16 16:10:02 Re: Question about optimising (Postgres_)FDW
Previous Message Robert Haas 2014-04-16 16:04:26 Re: bgworker crashed or not?