| From: | Ben Chobot <bench(at)silentmedia(dot)com> |
|---|---|
| To: | Scott Otis <scott(dot)otis(at)intand(dot)com> |
| Cc: | pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: Databases vs Schemas |
| Date: | 2009-10-09 18:18:09 |
| Message-ID: | 4ACF7E61.5020403@silentmedia.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Scott Otis wrote:
>
> I am seeking advice on what the best setup for the following would be.
>
>
>
> My company provides a hosted web calendaring solution for school
> districts. For each school district we have a separate database.
> Each database has 57 tables.
>
....
>
> Over the next couple of months we will be creating an instance of our
> solution for each public school district in the US which is around
> 18,000.
>
Why are you trying to keep all this information on one server? It seems
like you have such perfectly independent silos of data, why not take the
opportunity to scale out horizontally? It's usually a lot cheaper to buy
4 machines of power x than one machine of power (4x).
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Mielke | 2009-10-09 18:30:17 | Re: UUID as primary key |
| Previous Message | Tory M Blue | 2009-10-09 17:58:06 | Re: concurrent reindex issues |