Scalability Design Questions - Mailing list pgsql-general

From novnov
Subject Scalability Design Questions
Date
Msg-id 12571941.post@talk.nabble.com
Whole thread Raw
Responses Re: Scalability Design Questions  ("Scott Marlowe" <scott.marlowe@gmail.com>)
List pgsql-general
What happens when a database needs to scale beyond a single server? Is this
something PostgreSQL can do?

Further, does a database need to be designed differently if it's going to be
used on more than one server? I know there are many issues that might effect
a database's ability to scale; but specifically, will a well designed single
server database be easily adapted to multiple servers, or will the design
have to be adjusted? Example that might make the question more clear: from
my perspective, in terms of simplicity it'd be ideal if when a database is
deployed on multiple servers, the database responds as if it's simply
deployed on a more powerful box. But of course it may be more complicated
than that <g>.
--
View this message in context: http://www.nabble.com/Scalability-Design-Questions-tf4406693.html#a12571941
Sent from the PostgreSQL - general mailing list archive at Nabble.com.


pgsql-general by date:

Previous
From: "Scott Marlowe"
Date:
Subject: Re: Connection pooling
Next
From: "Scott Marlowe"
Date:
Subject: Re: Scalability Design Questions