pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Leví Teodoro da Silva <tlevisilva@gmail.com>
To: pgsql-performance@postgresql.org
Subject: Re: [QUESTION]Concurrent Access
Date: Mon, 14 Jul 2008 11:23:01 -0300
Message-ID: <4a74ba520807140723o2bb0af58q96772eaf62704fa7@mail.gmail.com> (raw)
In-Reply-To: <87hcb5ziuv.fsf@dba2.int.libertyrms.com>
References: <4a74ba520807021131l28308633yf0ad5416a7055f9@mail.gmail.com>
	<87hcb5ziuv.fsf@dba2.int.libertyrms.com>

Hi guys !!!

Sorry for the wrong spelling. =)
I could see that PostgreSQL will support my application, but i have to do a
good configuration on my server.

Thanks for answers, now i will look for informations about PostgreSQL on
OpenSolaris 2008.05
Have a nice week,
Levi


2008/7/4 Chris Browne <cbbrowne@acm.org>:

> tlevisilva@gmail.com ("Leví Teodoro da Silva") writes:
> > Hi guys, How are you ?
> > I am from Brazil and i work for a little company and it company is
> working is medium-big project and we want to use PostGree like the DataBase
> > system, but i got some questions.
> > I want to know if the PostGree has limitations about the concurrent
> access, 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
> use !? How big could be my database and how simultaneously access this
> > database support ?
>
> PostGree is a system I am not familiar with; this list is for
> discussion of PostgreSQL, sometimes aliased as "Postgres," so I will
> assume you are referring instead to PostgreSQL.
>
> PostgreSQL does have limitations; each connection spawns a process,
> and makes use of its own "work_mem", which has the result that the
> more connections you configure a particular backend to support, the
> more memory that will consume, and eventually your system will
> presumably run out of memory.
>
> The size of the database doesn't have as much to do with how many
> users you can support as does the configuration that you set up.
> --
> select 'cbbrowne' || '@' || 'linuxfinances.info';
> http://cbbrowne.com/info/lsf.html
> Rules  of the  Evil Overlord  #145. "My  dungeon cell  decor  will not
> feature exposed pipes.  While they add to the  gloomy atmosphere, they
> are good  conductors of vibrations and  a lot of  prisoners know Morse
> code." <http://www.eviloverlord.com/;
>
> --
> Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-performance
>

view thread (6+ messages)

Message-ID: <4a74ba520807140723o2bb0af58q96772eaf62704fa7@mail.gmail.com>
Permalink:  ../4a74ba520807140723o2bb0af58q96772eaf62704fa7@mail.gmail.com/
Also on:    postgresql.org/message-id/4a74ba520807140723o2bb0af58q96772eaf62704fa7@mail.gmail.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: tlevisilva@gmail.com
  Subject: Re: [QUESTION]Concurrent Access
  In-Reply-To: <4a74ba520807140723o2bb0af58q96772eaf62704fa7@mail.gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox