| From: | undisclosed user <lovetodrinkpepsi(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Experience with many schemas vs many databases |
| Date: | 2009-11-15 19:07:06 |
| Message-ID: | 995a16b70911151107m7f4c61f2j83504a443c5f7046@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
If I were to switch to a single DB/single schema format shared among all
users , how can I backup each user individually?
Frank
On Sat, Nov 14, 2009 at 10:28 PM, undisclosed user <
lovetodrinkpepsi(at)gmail(dot)com> wrote:
> Hello everyone,
>
> I have hit a wall on completing a solution I am working on. Originally, the
> app used a db per user (on MyIsam)....the solution did not fair so well in
> reliability and performance. I have been increasingly interested in Postgres
> lately.
>
> Currently, I have about 30-35k users/databases. The general table layout is
> the same....only the data is different. I don't need to share data across
> databases. Very similar to a multi-tenant design.
>
> Here are a few questions I have:
>
> 1. Could postgres support this many DBs? Are there any weird things that
> happen when the postgres is used this way?
> 2. Is the schema method better? Performance, maintainability, backups,
> vacuum? Weird issues?
>
>
> Any incite is greatly appreciated.
>
> Thanks.
> Frank
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Marlowe | 2009-11-15 19:25:26 | Re: Experience with many schemas vs many databases |
| Previous Message | Merlin Moncure | 2009-11-15 18:54:29 | Re: Experience with many schemas vs many databases |