From: | Alex Stapleton <alexs(at)advfn(dot)com> |
---|---|
To: | Alex Stapleton <alexs(at)advfn(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Michael Riess <mlriess(at)gmx(dot)de>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: 15,000 tables |
Date: | 2005-12-02 14:20:41 |
Message-ID: | C04CA26B-937E-4206-BD0A-D169D52A997A@advfn.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-es-ayuda pgsql-performance |
On 2 Dec 2005, at 14:16, Alex Stapleton wrote:
>
> On 1 Dec 2005, at 16:03, Tom Lane 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...)
>>
>
> Won't you end up with awful seek times if you just want data which
> previously been stored in a single table? E.g. whilst before you
> wanted 1000 contiguous rows from the table, now you want 1000 rows
> which now have 1000 rows you don't care about in between each one
> you do want.
>
I must of had a total and utter failure of intellect for a moment
there. Please ignore that :P
From | Date | Subject | |
---|---|---|---|
Next Message | Mario Gonzalez | 2005-12-02 14:29:29 | Re: Seguridad en tablas |
Previous Message | Jaime Casanova | 2005-12-02 14:20:25 | Re: usando like |
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Wieck | 2005-12-02 15:16:28 | Re: 15,000 tables |
Previous Message | Alex Stapleton | 2005-12-02 14:16:24 | Re: 15,000 tables |