From: | Jaime Casanova <systemguards(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Michael Riess <mlriess(at)gmx(dot)de>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: 15,000 tables |
Date: | 2005-12-01 16:15:00 |
Message-ID: | c2d9e70e0512010815h71c37d61hc9b13fa849493046@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-es-ayuda pgsql-performance |
On 12/1/05, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Michael Riess <mlriess(at)gmx(dot)de> writes:
> > (We NEED that many tables, please don't recommend to reduce them)
>
> No, you don't. Add an additional key column to fold together different
> tables of the same structure. This will be much more efficient than
> managing that key at the filesystem level, which is what you're
> effectively doing now.
>
> (If you really have 15000 distinct rowtypes, I'd like to know what
> your database design is...)
>
> regards, tom lane
>
Maybe he is using some kind of weird ERP... take the case of BaaN
(sadly i use it in my work): BaaN creates about 1200 tables per
company and i have no control of it... we have about 12000 tables
right now...
--
regards,
Jaime Casanova
(DBA: DataBase Aniquilator ;)
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Riess | 2005-12-01 16:28:44 | Re: 15,000 tables |
Previous Message | Jaime Casanova | 2005-12-01 16:06:11 | Re: Herramienta Graficadora Postgres |
From | Date | Subject | |
---|---|---|---|
Next Message | Merlin Moncure | 2005-12-01 16:15:05 | Re: pg_dump slow |
Previous Message | Michael Riess | 2005-12-01 16:04:06 | Re: 15,000 tables |