Search Postgresql Archives

multi-company design/structure ?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi,

Is it better to create multi databases or create multi schemas?

I am writing a program that can have multi instances.  Sort like a finanical 
accounting system that can have multiable companies. Where each company has a 
different name but the tables are an exact match to each other.  IOW the only 
difference between the company tables is the data that each instance 
contains. 

I believe that if I use multi-schemas within one database it will be easier to 
retrieve data from other schemas.  But what if the data has to be on 
different computers (or multi locations) - is it true I have to insure all 
the schemas are in the same data location?  Or can the schemas be on 
different computers.  

Anyway I'd like to hear from the list opinion as to the best way to design 
this structure.  

Also I believe the database/s will be run on Linux.

Thanks in advance,

Johnf

 


-- 
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux