Re: PostgreSQL transaction locking problem

At 08:51 PM 02-02-2002 -0800, Jeff Martin wrote:
>independent from the database server. Thus in a multi-user situation I
>gain. However, can I tune postgres to run several server processes as well?
>Can postgres run concurrent server processes in both persistant and
>non-persistant connection situations? I am beginning to think I should not
>have encapsulated my business logic in pg/sql but in PHP functions instead.

The persistent and nonpersistent stuff is done by PHP not by postgresql.
You just have to configure Postgresql to support the number of concurrent
backends you need.

The potential performance problem in your case is it's not as easy to scale
up the postgresql box - you are still limited to running it on one server
AFAIK. So if more of your processing is done by postgresql you'd hit the
limit sooner. Whereas if the PHP scripts bore the brunt of the CPU load,
then you could probably add cheap machines for the PHP stuff. That said has
anyone got postgresql running on an IBM mainframe :)? Pgbench figures would
be interesting...

Cheerio,
Link.