Skip site navigation (1) Skip section navigation (2)

Re: single task postgresql

From: Barry Lind <barry(at)xythos(dot)com>
To: mlw <markw(at)mohawksoft(dot)com>
Cc: Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>,PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: single task postgresql
Date: 2002-02-06 02:30:45
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
If you can improve the ipc implementation under cygwin that would be 
great.  Perhaps you could look at the source for the current 
(, and 
come up with a patch that would improve the performance/implmentation.


mlw wrote:
> Oleg Bartunov wrote:
>>we have to support earlier windows which have no shared memory support.
> I'm pretty sure it could a configuration option then. Using a file is just
> plain stupid. "Every" version of Windows has supported shared memory in one
> form or another.
> What version are you wishing to support which the cygwin guys claim does not
> have shared memory?
> I'm prety sure I can write a shared memory interface for Windows which should
> work across all "supported" versions.
> (BTW I have been a Windows developer since version 1.03.)
>>On Tue, 26 Feb 2002, mlw wrote:
>>>Oleg Bartunov wrote:
>>>>Having frustrated with performance on Windows box I'm wondering if it's
>>>>possible to get postgresql optimized for working without shared memory,
>>>>say in single-task mode. It looks like it's shared memory emulation on disk
>>>>(by cygipc daemon) is responsible for performance degradation.
>>>>In our project we have to use Windows for desktop application and it's
>>>>single task, so we don't need shared memory. In principle, it's possible
>>>>to hack cygipc, so it wouldn't emulate shared memory and address calls
>>>>to normal memory, but I'm wondering if it's possible from postgres side.
>>>>        Regards,
>>>How does cygwin do shared memory on Windows? Windows support real shared
>>>memory, surely the cygwin guys are using "real" shared memory. Are you sure
>>>that this is the problem? If so, might we not be able to use a few
>>>macros/#ifdefs to do it right?
>>>I'll be up for that if you guys don't mind some "ifdef/endif" stuff here and
>>        Regards,
>>                Oleg
>>Oleg Bartunov, sci.researcher, hostmaster of AstroNet,
>>Sternberg Astronomical Institute, Moscow University (Russia)
>>Internet: oleg(at)sai(dot)msu(dot)su,
>>phone: +007(095)939-16-83, +007(095)939-23-83
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?

In response to

pgsql-hackers by date

Next:From: Peter EisentrautDate: 2002-02-06 03:34:10
Subject: Re: PostgreSQL v7.2 Final Release
Previous:From: Christopher Kings-LynneDate: 2002-02-06 02:03:21
Subject: Re: Display of TIMESTAMP in 7.2

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group