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

Re: Re: useability of apache, PHP, Postgres for real business apps

From: GH <grasshacker(at)over-yonder(dot)net>
To: Micah Yoder <yodermk(at)home(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Re: useability of apache, PHP, Postgres for real business apps
Date: 2001-06-30 01:17:01
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-general
On Fri, Jun 29, 2001 at 05:26:08PM -0400, some SMTP stream spewed forth: 
> > Not exactly.
> > Pretend the following:
> > You have 3 database users (usernames) using persistent connections.
> > In the simplest case, you need 3 PostgreSQL backends to support one each
> > of those users. That means you need 3 backends per httpd process.
> > 10 concurrent httpd clients => 30 PostgreSQL backends.
> Well I only need to connect from one database user -- nobody.  But my 
> pg_pconnect string specifies the database to use -- pg_pconnect("dbname=otg 
> host=localhost port=5432"); 
> And there are (or will be) other databases on the system, but all will 
> probably connect from nobody.  Does pconnect use the same connection for 
> different databases if it is from the same user?

I apologize for not being clear, entirely my fault:
No, each user/database pair uses a connection. Same user, different
database -> another connection.

> > Yep, ouch. In an extreme case, you might want to check out AOLServer for
> > its pooling stuff. Technically, you only need enough ram to support the
> Might not be a bad idea.  Does it support PHP and virtual hosts and all that 
> as well as Apache?

I have no idea. I have never used it in production. AOLServer  has 
native TCL support, which is kind of cool if you are into that sort 
of thing. It is threaded, so reliability is on PHP's side of the fence.
Last I heard, (long time ago, by the way) PHP's threading worked, but was
not 100%. The PHP people probably have that all sorted out by now, so you
should be fine.

It does support virtual host and PHP, but it is threaded, so a comparison
to Apache would be a bit odd. Everything I have heard claims that
AOLServer is hella-fast and efficient. It is definitely worth taking a
weekend to checkout (which, unfortunately, is where my experience with it
ends). If nothing else, the connection pooling should make up for any
other speed issues.


> -- 
> Like to travel?              
> Micah Yoder Internet Development

In response to


pgsql-general by date

Next:From: Tatsuo IshiiDate: 2001-06-30 01:18:58
Subject: Re: multibyte tables
Previous:From: GHDate: 2001-06-29 23:10:16
Subject: Re: Re: useability of apache, PHP, Postgres for real business apps

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