| From: | Richard Huxton <dev(at)archonet(dot)com> |
|---|---|
| To: | Karsten Hilbert <Karsten(dot)Hilbert(at)gmx(dot)net>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: inheritance vs performance |
| Date: | 2004-02-13 13:51:24 |
| Message-ID: | 200402131351.24474.dev@archonet.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Friday 13 February 2004 10:59, Karsten Hilbert wrote:
> > Well, thousands of tables is probably "too much", but a hundred tables or
> > two in a database shouldn't cause problems. Don't see why you'd want them
> > though.
>
> If that's your general advice (a hundred or more tables in a
> database not making sense) I should like to learn why. Is that
> a sure sign of overdesign ? Excess normalization ? Bad
> separation of duty ? I am asking since our schema is at
> about 200 relations and growing.
The original mail mentioned many "C tables" all with the same columns.
Obviously you need as many different tables as required to model your data,
but many tables all with identical schema?
--
Richard Huxton
Archonet Ltd
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Csaba Nagy | 2004-02-13 14:35:08 | Re: inheritance vs performance |
| Previous Message | Andrew Sullivan | 2004-02-13 12:35:35 | Re: Idle Connection force-close ? |