On Thu, Dec 8, 2011 at 9:11 AM, Marc Cousin <cousinmarc@gmail.com> wrote:
> Le Thu, 8 Dec 2011 12:27:22 +0000,
> Simon Riggs <simon@2ndQuadrant.com> a écrit :
>
>> On Thu, Dec 8, 2011 at 11:24 AM, Craig Ringer <ringerc@ringerc.id.au>
>> wrote:
>>
>> > Areas in which Pg seems significantly less capable include:
>>
>> Please can you explain the features Oracle has in these area, I'm not
>> clear. Thanks.
>
> Maybe I can answer from my own Oracle experience. I hope it will be what
> Craig had in mind :)
>
>>
>>
>> > - admission control, queuing and resource limiting to optimally
>> > load a machine. Some limited level is possible with external
>> > pooling, but only by limiting concurrent workers.
>
> Oracle has natively two ways of handling inbound connections:
> - Dedicated, which is very similar to the PostgreSQL way of accepting
> connections: accept(), fork() and so on
> - Shared, which is based on processes listening and handling the
> connections (called dispatchers) and processes doing the real work
> (called workers, obviously). All of this works internally with
> some sort of queuing and storing results in shared memory (I don't
> remember the details of it)
>
> The advantage of this second architecture being of course that you
> can't have more than N workers hitting your database simultaneously. So
> it's easier to keep the load on the server to a reasonable value.
you have a couple of very good options to achieve the same in postgres
-- pgbouncer, pgpool.
merlin