Thread: Re: [GENERAL] splitting tables into db's

Re: [GENERAL] splitting tables into db's

From
Nemeth Miklos
Date:
> > If there are too many requests for a particular database, is there a way
> > for postgresql to do load balancing across multiple servers? As far as I
> > can see, the only way would be to split the tables within the database
> > into distinct databases. Of course, this would assume there are no
> > dependencies between each database. This can obviously cause a problem, so
> > are there any recommended ways to have a form of load balancing with
> > postgresql?
>
> There is no build-in load balancing in PostgreSQL.
>
> As an alternative I would use an database-mirror.
> For read-Queries the application can use any of the servers.
> For Updates the application has to send them to all servers.
>
>
Just a simple comment.

Even very expensive commercial database engines (like Oracle,
ObjectStore, etc) does not provide any kind of load balancing.
And even wors no connection pooling.
PostgreSQL follows the DBMS norm.

NM




Re: [GENERAL] splitting tables into db's

From
Dustin Sallings
Date:
On Thu, 17 Feb 2000, Nemeth Miklos wrote:

# Even very expensive commercial database engines (like Oracle,
# ObjectStore, etc) does not provide any kind of load balancing.
# And even wors no connection pooling.
# PostgreSQL follows the DBMS norm.

    Check out Sybase's OpenSwitch.

--
SA, beyond.com           My girlfriend asked me which one I like better.
pub  1024/3CAE01D5 1994/11/03 Dustin Sallings <dustin@spy.net>
|    Key fingerprint =  87 02 57 08 02 D0 DA D6  C8 0F 3E 65 51 98 D8 BE
L_______________________ I hope the answer won't upset her. ____________