spreading the DB?

[raptor]

hi,

what do u do if the DB become big and u have to spread
it into two or more computers.
Links and Docs are ok too ?

For example what if u do if u want to split the DB on two servers (at desing stage), but
u have common data such as user info,address etc... if u decide to do it that way
u need to syncronize common data in some way, what do u do.
tia

---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster

[Richard Huxton]

raptor wrote:

hi,

what do u do if the DB become big and u have to spread
it into two or more computers.
Links and Docs are ok too ?

For example what if u do if u want to split the DB on two servers (at desing stage), but
u have common data such as user info,address etc... if u decide to do it that way
u need to syncronize common data in some way, what do u do.

It's called "replication" - you should probably spend some time reading
up on the issues it presents. The current most-popular system would seem
to be "Slony".

--
Richard Huxton
Archonet Ltd

---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faqs/FAQ.html

[Richard Huxton]

raptor wrote:

hi,

what do u do if the DB become big and u have to spread
it into two or more computers.
Links and Docs are ok too ?

For example what if u do if u want to split the DB on two servers (at desing stage), but
u have common data such as user info,address etc... if u decide to do it that way
u need to syncronize common data in some way, what do u do.

It's called "replication" - you should probably spend some time reading
up on the issues it presents. The current most-popular system would seem
to be "Slony".

--
Richard Huxton
Archonet Ltd

---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faqs/FAQ.html