databases in postgres

[nightowl]

i have this postgres running locally and can choose between creating multiple databases to store my tables. That way, they would be kept together in a logical way. I can also choose to store them in 1 db and create mutiple views (using PhpPgAdmin). What would be the best thing to do? What are the differences? does postgres without that interface understand views ?

[smarlowe]

Related data should live in the same database for performance and administrative ease. If you're writing one app that's for time scheduling, and another for swapping mp3s, there's no reason for those two to be in the same database. If you're writing a calendar and a conference room scheduler, they should probably go into the same database, since they'll like have to interoperate.

[nightowl]

thanks for the reply.

I had this conversation with my former host-webmaster and he mentioned that "the number of databases on the system had to be kept low". Didn't know why, but happy to know that it shouldn"t be a problem to create and manage some more db on a system...

[smarlowe]

I've run dozens of databases from one postgresql instance with no problems with performance or memory usage. So, you should be fine with a few extra floating around.