Re: [PATCH] "could not reattach to shared memory" on Windows - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: [PATCH] "could not reattach to shared memory" on Windows
Date
Msg-id 20090714140237.GD4799@alvh.no-ip.org
Whole thread Raw
In response to [PATCH] "could not reattach to shared memory" on Windows  (Tsutomu Yamada <tsutomu@sraoss.co.jp>)
Responses Re: [PATCH] "could not reattach to shared memory" on Windows  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: [PATCH] "could not reattach to shared memory" on Windows  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
List pgsql-hackers
Tsutomu Yamada wrote:

> This patch using VirtualAlloc()/VirtualFree() to avoid failing in
> reattach to shared memory.
> 
> Can this be added to CommitFest ?

Since this fixes a very annoying bug present in older versions, I think
this should be backpatched all the way back to 8.2.

Some notes about the patch itself:

- please use ereport() instead of elog() for error messages
- Are you really putting the pgwin32_ReserveSharedMemory declaration
inside a function?  Please move that into the appropriate header file.
- Failure to reserve memory in pgwin32_ReserveSharedMemory should be a
FATAL error I think, not simply LOG.



-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.


pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Synch Rep for CommitFest 2009-07
Next
From: Alvaro Herrera
Date:
Subject: Re: Comments on automatic DML routing and explicit partitioning subcommands