Re: OK, lets talk portability.

From: "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au>
To: "mlw" <markw(at)mohawksoft(dot)com>, "Dann Corbit" <DCorbit(at)connx(dot)com>
Cc: "PostgreSQL-development" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: OK, lets talk portability.
Date: 2002-05-08 01:57:23
Message-ID: GNELIHDDFBOCMGBFGEFOKEHPCCAA.chriskl@familyhealth.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Just a note:

Apache 2.0.36 just released and this is in the release notes:

*) Deprecated the apr_lock.h API. Please see the following files
for the improved thread and process locking and signaling:
apr_proc_mutex.h, apr_thread_mutex.h, apr_thread_rwlock.h,
apr_thread_cond.h, and apr_global_mutex.h. [Aaron Bannert]

Chris

> > By the time of the fork(), not much has been done. Some needed
> > calculations can simply be stored into shared memory (which is trivial
> > to implement). Some other tasks can simply be executed by the cloned
> > process, exactly as they were executed in the server.
> >
> > Using fork() on Win32 is pointless, hopless, awful. Don't even think
> > about it. It's a death warrant.
>
> Preaching to the choir my friend.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Christopher Kings-Lynne 2002-05-08 02:05:21 Re: code contribution
Previous Message Ryan Bradetich 2002-05-08 01:42:04 Re: a couple of minor itches: RI Trigger Names, and