On Thu, Jul 03, 2003 at 10:18:23 +0800,
  Christopher Kings-Lynne <chriskl@familyhealth.com.au> wrote:
> 
> It might be killer than that PHP support for Apache2 requires that all PHP
> modules be thread-safe...

Is that true if you are using the prefork MPM?

Thu, 3 Jul 2003 06:31:38 -0500
Bruno Wolff III <bruno@wolff.to>
Re: 7.4 feature freeze is here
> On Thu, Jul 03, 2003 at 10:18:23 +0800,
>   Christopher Kings-Lynne <chriskl@familyhealth.com.au> wrote:
> >
> > It might be killer than that PHP support for Apache2 requires that all
PHP
> > modules be thread-safe...
>
> Is that true if you are using the prefork MPM?

Dunno.

Chris


Fri, 4 Jul 2003 09:44:06 +0800
"Christopher Kings-Lynne" <chriskl@familyhealth.com.au>
Re: 7.4 feature freeze is here
Folks,

> > You might like to mention that (as far as I can tell) ECPG is now safe
> > for pthreads on Linux and FreeBSD. The recursive mutex locks are removed,
> > so
>
> even
>
> > platforms that implement the earlier version of pthreads ought to work as
> > well, once configure supports them (anyone care to actually test this
> > assertion?)

I don't quite understand this.  This doesn't mean that *postgresql* is 
threaded, does it?



-- 
Josh Berkus
Aglio Database Solutions
San Francisco

Thu, 3 Jul 2003 23:03:41 -0700
Josh Berkus <josh@agliodbs.com>
Re: 7.4 feature freeze is here
On Fri, 4 Jul 2003 04:03 pm, Josh Berkus wrote:
> I don't quite understand this.  This doesn't mean that *postgresql* is
> threaded, does it?

I was just referring to the client interfaces ECPG and libpq. AFAIK the 
back-end is not threaded (and I'm beginning to understand why not).

So my app starts multiple threads of execution through the ECPG libs... the 
ECPG libs (and libpq) start multiple sockets to the back-end - one for each 
thread. No changes to the back-end. 

That's my understanding - Lee did most of the work, so maybe he can confirm 
that.

Regards, Philip Yarra.


Fri, 4 Jul 2003 16:15:28 +1000
Philip Yarra <philip@utiba.com>
Re: 7.4 feature freeze is here