Re: Connection Pooling directly on Postgres Server

From: Denis Gasparin <denis(at)edistar(dot)com>
To: Markus Schiltknecht <markus(at)bluegap(dot)ch>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Connection Pooling directly on Postgres Server
Date: 2007-09-08 07:10:55
Message-ID: 46E24AFF.7030404@edistar.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general


> This has certainly been discussed before.
>
> IIRC the real argument against that was, that fork() isn't the most
> expensive thing to do anymore. And Postgres does lots of other stuff
> after accept(), namely connecting to a certain database,
> authenticating the user, etc..
Ok. I knew that. I made the question because it seems that, for example,
Oracle in release 11g is moving to a similar solution in order to solve
connection pooling problems.

For example look at the following link:

http://pbarut.blogspot.com/2007/08/oracle-11g-drcp-database-resident.html

Denis

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Richard Huxton 2007-09-08 07:26:04 Re: replacing Access/ Approach etc
Previous Message Zenaan Harkness 2007-09-08 05:03:54 replacing Access/ Approach etc