Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id E5D12650EC2 for ; Wed, 2 Jul 2008 15:47:56 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 92928-04 for ; Wed, 2 Jul 2008 15:47:29 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from qb-out-0506.google.com (qb-out-0506.google.com [72.14.204.234]) by postgresql.org (Postfix) with ESMTP id B84E9650EB3 for ; Wed, 2 Jul 2008 15:47:24 -0300 (ADT) Received: by qb-out-0506.google.com with SMTP id c8so1540366qbc.39 for ; Wed, 02 Jul 2008 11:47:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:cc:in-reply-to:mime-version:content-type :content-transfer-encoding:content-disposition:references; bh=U7zQjbu0N0SfH53Ekl2bfELyU+5VUtqp7x50AhdyfDQ=; b=abd5VVyf1aY2QGbFx/SRfpZID+cn/zufRxGHAp5OR6yFyThTUjrU53eDllP38uAtPr RjNbnlMpdXmtJu1BTYtBxtxMlQ19PWmhK2bw45F0eL+aY0jzt5sIl2H2lsaKQ+EiBGkj Gncv5O7PlWzUv52e/SsQg8FA+dCAEYQWpE/nI= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:cc:in-reply-to:mime-version :content-type:content-transfer-encoding:content-disposition :references; b=rQr7tV1JsIWHeZKpTThW+pvpKY0wZGY8WkxNLaBsD+viltTzdyJaW5uvieCu5387U9 yGE0x5cnywjXYCu0/qksdiSX88rsBlKnPIHVfE7JaTQ2R4yy6rXaNuqQqcRxpExuQ67I 0WzdQAhNfVif7Yynqofit/fMuppHTWCLTSQ8g= Received: by 10.115.89.1 with SMTP id r1mr7382534wal.12.1215024443696; Wed, 02 Jul 2008 11:47:23 -0700 (PDT) Received: by 10.114.180.17 with HTTP; Wed, 2 Jul 2008 11:47:23 -0700 (PDT) Message-ID: Date: Wed, 2 Jul 2008 12:47:23 -0600 From: "Scott Marlowe" To: "=?ISO-8859-1?Q?Lev=ED_Teodoro_da_Silva?=" Subject: Re: [QUESTION]Concurrent Access Cc: pgsql-performance@postgresql.org In-Reply-To: <4a74ba520807021131l28308633yf0ad5416a7055f9@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <4a74ba520807021131l28308633yf0ad5416a7055f9@mail.gmail.com> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200807/33 X-Sequence-Number: 30633 On Wed, Jul 2, 2008 at 12:31 PM, Lev=ED Teodoro da Silva wrote: > Hi guys, How are you ? > > > I am from Brazil and i work for a little company and it company is workin= g > is medium-big project and we want to use PostGree like the DataBase syste= m, > but i got some questions. > I want to know if the PostGree has limitations about the concurrent acces= s, > because a lot of people will access this database at the same time. > I want to know about the limitations, like how much memory do i have to u= se > !? How big could be my database and how simultaneously access this databa= se > support ? There is a limit that's basically determined by the machine you're running on. Each live connection uses a bit of memory itself and there can be a few thundering herd issues with a lot of connections. that said, a big server, properly configured can handle several hundred to a few thousand connections at once. We have simple little session servers that store most of what they do in memory and handle around 700 connections with a single SATA hard drive. The data is disposable so fsync is off and we can just rebuilt one from an image in minutes if need be.