On Mon, 6 May 2002, mlw wrote:
> Tom Lane wrote:
> >
> > "Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> > > Well, I guess that just saved *me* alot of work ... thanks ...
> >
> > Uh, not yet. Don't you still need a semaphore implementation that
> > works on Windows?
> >
>
> I have a LOT of exp
> Well, SharedMemoryIsInUse is *not* just about ensuring that the shared
> memory gets reaped. The point is to ensure that you can't start a new
> postmaster until the last old backend is gone. (Consider situations
> where the parent postmaster process crashes, or perhaps is kill -9'd
> by a car
"Cyril VELTER" <[EMAIL PROTECTED]> writes:
> Are the PGShmemHeader fields only used by PGSharedMemoryCreate ?
Other than totalsize and freeoffset, I believe so. I see no reason
that a particular port couldn't stick different fields in there if it
had a mind to.
>> How does that solve the pr
On Sat, 2002-05-04 at 21:56, Tom Lane wrote:
> mlw <[EMAIL PROTECTED]> writes:
> > We could provide a PGSemaphore based on an APR mutex and a counter,
> > but I'm not sure of the performance impact. We may want to implement a
> > "generic" semaphore like this and one optimized for platforms which
On Mon, 6 May 2002, Tom Lane wrote:
> "Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> > Well, I guess that just saved *me* alot of work ... thanks ...
>
> Uh, not yet. Don't you still need a semaphore implementation that
> works on Windows?
Yup ... next steps, but I believe that is what Mark i
On Sat, 2002-05-04 at 21:56, Tom Lane wrote:
> mlw <[EMAIL PROTECTED]> writes:
> > We could provide a PGSemaphore based on an APR mutex and a counter,
> > but I'm not sure of the performance impact. We may want to implement
a
> > "generic" semaphore like this and one optimized for platforms which
> "Cyril VELTER" <[EMAIL PROTECTED]> writes:
> > Also why not do the header fillup outside of PGSharedMemoryCreate ?
>
> Well, (a) I wasn't really concerned about defining an all-new API for
> shmem, and (b) I think the header is largely dependent on the semantics
> of SysV shmem anyway. A di
Tom Lane wrote:
>
> "Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> > Well, I guess that just saved *me* alot of work ... thanks ...
>
> Uh, not yet. Don't you still need a semaphore implementation that
> works on Windows?
>
I have a LOT of experience with Windows development. You tell me wh
"Marc G. Fournier" <[EMAIL PROTECTED]> writes:
> Well, I guess that just saved *me* alot of work ... thanks ...
Uh, not yet. Don't you still need a semaphore implementation that
works on Windows?
regards, tom lane
---(end of broadcast)---
Well, I guess that just saved *me* alot of work ... thanks ...
On Sat, 4 May 2002, Tom Lane wrote:
> mlw <[EMAIL PROTECTED]> writes:
> > We could provide a PGSemaphore based on an APR mutex and a counter,
> > but I'm not sure of the performance impact. We may want to implement a
> > "generic" s
On Sat, 4 May 2002, mlw wrote:
> Upon doing some inspection of apache 2.x, it seems that me making a SysV
> Windows .DLL for PostgreSQL, while a cool project, would be unnecessary.
>
> The APR (Apache Portable Runtime) seems to have all the necessary support. The
> problem is that it has its own
"Cyril VELTER" <[EMAIL PROTECTED]> writes:
> I find the semaphore API quite clean but have some question on the
> Shared memory one. The Id's passed to PGSharedMemoryIsInUse aren't clear to
> me. How id1 and id1 are related to the port parameter of
> PGSharedMemoryCreate ?
You can define 'em
AIL PROTECTED]>
Sent: Saturday, May 04, 2002 6:56 PM
Subject: Re: [HACKERS] Native Windows, Apache Portable Runtime
> mlw <[EMAIL PROTECTED]> writes:
> > We could provide a PGSemaphore based on an APR mutex and a counter,
> > but I'm not sure of the performance i
mlw <[EMAIL PROTECTED]> writes:
> We could provide a PGSemaphore based on an APR mutex and a counter,
> but I'm not sure of the performance impact. We may want to implement a
> "generic" semaphore like this and one optimized for platforms which we
> have development resources.
Once we have the in
Tom Lane wrote:
>
> mlw <[EMAIL PROTECTED]> writes:
> > Upon doing some inspection of apache 2.x, it seems that me making a SysV
> > Windows .DLL for PostgreSQL, while a cool project, would be unnecessary.
>
> > The APR (Apache Portable Runtime) seems to have all the necessary support.
>
> Does
mlw <[EMAIL PROTECTED]> writes:
> Upon doing some inspection of apache 2.x, it seems that me making a SysV
> Windows .DLL for PostgreSQL, while a cool project, would be unnecessary.
> The APR (Apache Portable Runtime) seems to have all the necessary support.
Does it? AFAICT they intend to provi
Justin Clift wrote:
>
> mlw wrote:
> >
> > Upon doing some inspection of apache 2.x, it seems that me making a SysV
> > Windows .DLL for PostgreSQL, while a cool project, would be unnecessary.
> >
> > The APR (Apache Portable Runtime) seems to have all the necessary support. The
> > problem is th
mlw wrote:
>
> Upon doing some inspection of apache 2.x, it seems that me making a SysV
> Windows .DLL for PostgreSQL, while a cool project, would be unnecessary.
>
> The APR (Apache Portable Runtime) seems to have all the necessary support. The
> problem is that it has its own API.
>
> We shou
Upon doing some inspection of apache 2.x, it seems that me making a SysV
Windows .DLL for PostgreSQL, while a cool project, would be unnecessary.
The APR (Apache Portable Runtime) seems to have all the necessary support. The
problem is that it has its own API.
We should find a way to extract the
19 matches
Mail list logo
