Re: Is there any limitations

From: Nikk Anderson <Nikk(dot)Anderson(at)parallel(dot)ltd(dot)uk>
To: pgsql-performance(at)postgresql(dot)org
Subject: Re: Is there any limitations
Date: 2002-12-03 13:41:14
Message-ID: DA1274E682D3734B8802904A9B36124C298AEF@nic-nts1.nic.parallel.ltd.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Hi Li Li,

>
> I'm thinking about separating a table with up to millions of rows into
> several tables with the same set of columns to speed up some complex
> queries.

I thought of doing this recently, as queries were taking so long. Instead
of breaking the table up, we clustered the data. This physically moves all
the data by key close to each other on disk (sounds kind of like defragging
a disk). This boosts query responses no end - for example our table has ~
10 million rows, a query that was taking 45 seconds to return, now takes 7
seconds. To keep the table tidy, we run the cluster regularly.

> As the size of the original table is increasing fast, I want
> to get it separated once the size grows up to a limit. So there
> will be a large amount of tables (having same structure) in a
> database. Is
> there any potential performance problem with this design?
>

I think the problems would mainly be in management, as you would have to
keep track of the new table names, key names, and index names.

Nikk

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Tom Lane 2002-12-03 14:35:16 Re: v7.2.3 versus v7.3 -> huge performance penalty for JOIN with UNION
Previous Message Andrew Sullivan 2002-12-03 12:34:04 Re: Is there any limitations