Re: BUG #4738: Cannot reconnect to shared memory

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Jonathan Barnhart <jdbarnhart(at)yahoo(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #4738: Cannot reconnect to shared memory
Date: 2009-04-09 16:54:27
Message-ID: 200904091654.n39GsRj15139@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


Has there been any progress on this?

---------------------------------------------------------------------------

Jonathan Barnhart wrote:
>
> The following bug has been logged online:
>
> Bug reference: 4738
> Logged by: Jonathan Barnhart
> Email address: jdbarnhart(at)yahoo(dot)com
> PostgreSQL version: 8.3.7
> Operating system: WinXP, Vista
> Description: Cannot reconnect to shared memory
> Details:
>
> This bug seems to have been reintroduced between versions 8.3.4 and 8.3.7.
> It is basically a race condition when the fork emulation for Windows is
> used. The problem is that the side of the "fork" that creates the shared
> memory to emulate the Unix fork is often executed AFTER the logic in the
> "forked" process that connects to the shared memory.
>
> The obvious thing that has to be done is to create the shared memory object
> and THEN spawn the child processes. Unfortunately, the logic in that area
> is not entirely straightforward with a number of dependancies.
>
> I'm working on patching this, but so far I have had issues with screwing up
> other order dependant code.
>
> --
> Sent via pgsql-bugs mailing list (pgsql-bugs(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-bugs

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2009-04-09 16:55:16 Re: Re: [BUGS] BUG #4027: backslash escaping not disabled inplpgsql
Previous Message Bruce Momjian 2009-04-09 16:48:22 Re: possible bug not in open items