pg.ddx.io  pgsql-interfaces@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Frank Joerdens <frank@joerdens.de>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Tom Samplonius <tom@sdf.com>
Cc: mlw <markw@mohawksoft.com>
Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>
Cc: PostgreSQL-interfaces <pgsql-interfaces@postgresql.org>
Subject: Re: [INTERFACES] Re: PHP and PostgreSQL
Date: Wed, 03 Jan 2001 14:44:32 +0100
Message-ID: <3A532CC0.847FF3C7@joerdens.de> (raw)
References: <Pine.BSF.4.05.10101022030040.8582-100000@misery.sdf.com>
	<15332.978502036@sss.pgh.pa.us>

Tom Lane wrote:
[ . . . ]
> A general-purpose connection-reuse facility on the server end cannot
> eliminate these overheads, whereas it's trivial to avoid them within
> the context of a multi-threaded client.

PHP 4.04 does provide support for AOLServer now (which is multithreaded). I haven't had
time to play with it, and it moreover isn't certified for production use yet:

---------------------------------- snip ----------------------------------
NOTE: You should not use this module in production. PHP is not 100% stable
      yet in threaded mode. To increase reliability enable the Global Lock
      by removing #define NO_GLOBAL_LOCK in main/main.c. Also don't use
      php_value as it will lead to races in a sub-system (use an ini file
      instead).
---------------------------------- snap ----------------------------------
(from the php/sapi/aolserver/README)

But it might be the way to go forward with the connection pooling issue. Maybe the PHP
people could use some help from the Postgres developers there? I think it has been pointed
out in the context of this thread that Apache, as a multi-process server, could not
properly handle connection pooling because it's not feasible to pool connections across
several Apache children (or was that the problem?).

Regards, Frank



view thread (27+ messages)  latest in thread

Message-ID: <3A532CC0.847FF3C7@joerdens.de>
Permalink:  ../3A532CC0.847FF3C7@joerdens.de/
Also on:    postgresql.org/message-id/3A532CC0.847FF3C7@joerdens.de

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-interfaces@postgresql.org
  Cc: frank@joerdens.de, tgl@sss.pgh.pa.us, tom@sdf.com, markw@mohawksoft.com, pgsql-hackers@postgresql.org
  Subject: Re: [INTERFACES] Re: PHP and PostgreSQL
  In-Reply-To: <3A532CC0.847FF3C7@joerdens.de>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox