Re: Strategies/Best Practises Handling Large Tables - Mailing list pgsql-general

From John R Pierce
Subject Re: Strategies/Best Practises Handling Large Tables
Date
Msg-id 507849E4.8060508@hogranch.com
Whole thread Raw
In response to Strategies/Best Practises Handling Large Tables  (Chitra Creta <chitracreta@gmail.com>)
Responses Re: Strategies/Best Practises Handling Large Tables  (Chitra Creta <chitracreta@gmail.com>)
List pgsql-general
On 10/12/12 7:44 AM, Chitra Creta wrote:
>
> 1. Purge old data
> 2. Reindex
> 3. Partition
> 4. Creation of daily, monthly, yearly summary tables that contains
> aggregated data specific to the statistics required
>

if most of your queries read the majority of the tables,  indexing will
be of little help

parittioning will aid in purging old data, as you can partitions by date
(for instance, by week) and drop whole partitions rather than deleting
individual records.

aggregate tables likely will be the biggest win for your statistics if
they reduce the mount of data you need to query.


--
john r pierce                            N 37, W 122
santa cruz ca                         mid-left coast



pgsql-general by date:

Previous
From: José Pedro Santos
Date:
Subject: PostgreSQL and WMS
Next
From: salah jubeh
Date:
Subject: Re: PostgreSQL and WMS