X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id A12CF5696C for ; Sat, 19 Mar 2005 03:06:54 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 38291-06 for ; Sat, 19 Mar 2005 03:06:47 +0000 (GMT) Received: from svr2.postgresql.org (unknown [65.19.161.25]) by svr1.postgresql.org (Postfix) with ESMTP id A0FF156A3C for ; Sat, 19 Mar 2005 03:05:02 +0000 (GMT) Received: from ceroriesgo.co.cr (unknown [196.40.18.42]) by svr2.postgresql.org (Postfix) with ESMTP id 6FF04F0D3E for ; Fri, 18 Mar 2005 16:13:47 +0000 (GMT) Received: from [192.168.0.110] by ceroriesgo.co.cr (MDaemon.PRO.v7.2.3.R) with ESMTP id md50000014831.msg for ; Fri, 18 Mar 2005 10:16:58 -0800 Message-ID: <423AFEED.2020205@ceroriesgo.co.cr> Date: Fri, 18 Mar 2005 10:16:45 -0600 From: Sabio - PSQL User-Agent: Mozilla Thunderbird 1.0 (X11/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: PostgreSQL Admin Subject: Re: large database versus many databases References: <6.0.1.1.0.20050318145502.00a12e50@mx0.kiss-net.de> In-Reply-To: <6.0.1.1.0.20050318145502.00a12e50@mx0.kiss-net.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Authenticated-Sender: slopez@ceroriesgo.co.cr X-Spam-Processed: ceroriesgo.co.cr, Fri, 18 Mar 2005 10:16:58 -0800 (not processed: message from valid local sender) X-MDRemoteIP: 192.168.0.110 X-Return-Path: slopez_pg@ceroriesgo.co.cr X-MDaemon-Deliver-To: pgsql-admin@postgresql.org X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests= X-Spam-Level: X-Archive-Number: 200503/297 X-Sequence-Number: 16795 Uwe Maiwald wrote: > Hi, > > we are currently planning a very large installation of a > web-application using PostgreSQL. The application can be configured to > handle 1 database per customer, or all customers in one large database. > > We plan to start with e.g. 500 customers, each of which can have 200 > MB or more in the database. And we want the system to be expandable as > needed (thousands of customers, using lots of memory). > > Has anyone any experience what is best > - using one very large database for all customers or > - using 1 database per customer > > concerning expandability, performance, server configuration, system > updates etc. > > Is it advisable not to install more than a certain amount of databases > on one server? > > Any hints welcome, > > Thanks, Uwe > > > ---------------------------(end of broadcast)--------------------------- > TIP 6: Have you searched our list archives? > > http://archives.postgresql.org > > I am currently developing a system like this and we are using one database per customer. You only have to consider one thing. If you have only one database for all customer and database have a problem all customer can't work. If you have many databases as customers if a database fails only one customer can't work, and it's easier to solve for one that for all.