From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Chris Bitmead <chrisb(at)nimrod(dot)itg(dot)telstra(dot)com(dot)au> |
Cc: | nonsolosoft(at)diff(dot)org, pgsql-hackers(at)hub(dot)org |
Subject: | Re: MySQL comparison |
Date: | 2000-07-19 04:51:24 |
Message-ID: | 20054.963982284@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Chris Bitmead <chrisb(at)nimrod(dot)itg(dot)telstra(dot)com(dot)au> writes:
> Ferruccio Zamuner wrote:
>> PostgreSQL has a number of back-end processes defined at compile time, by
>> default 32.
> thread/process isn't that important. We even used to beat the opposition
> in number of databases/connections, by a huge margin. It's an
> implementation detail. Don't confuse people by throwing it up.
Another point worth making is that this is not a number fixed at compile
time, but just a postmaster parameter with a default of 32. You can set
it much higher if your system can handle the load.
The reason the default limit is so low is just that we'd like the code
to run out-of-the-box on platforms with small kernel limits on shared
mem or number of semaphores. The hidden assumption is that someone
who really needs a higher limit will know enough to RTFM ;-)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Stephan Szabo | 2000-07-19 05:25:26 | Re: [HACKERS] Re: PRIMARY KEY & INHERITANCE (fwd) |
Previous Message | Chris Bitmead | 2000-07-19 03:56:35 | Re: PRIMARY KEY & INHERITANCE (fwd) |