Re: Partitioning, Identity and Uniqueness (given pg 16 changes) - Mailing list pgsql-general

From Greg Sabino Mullane
Subject Re: Partitioning, Identity and Uniqueness (given pg 16 changes)
Date
Msg-id CAKAnmmJnHn8Z+E=+-XqZi6J=AV9-RTto4e3tc0RvMXbkq1Zmrg@mail.gmail.com
Whole thread Raw
In response to Partitioning, Identity and Uniqueness (given pg 16 changes)  (Darryl Green <darryl.green@gmail.com>)
List pgsql-general
I have a table that is capturing what is, basically, time series data

Time series data usually is concerned with "recent" data, and has a subsequent drop off date. This is ideal for partitioning by timestamp - not only do your queries only need to hit a few of the total tables, but you can simply drop old tables that contain older data. Optionally saving them first to deep storage. The DROP TABLE approach is extraordinarily better than the alternative of DELETE FROM ... WHERE ...

Cheers,
Greg

pgsql-general by date:

Previous
From: Moreno Andreo
Date:
Subject: Re: [SPAM] Re: Partial table duplication via triggger
Next
From: yudhi s
Date:
Subject: Creating table and indexes for new application