Re: Partitioning, Identity and Uniqueness (given pg 16 changes)

From: Greg Sabino Mullane <htamfids(at)gmail(dot)com>
To: Darryl Green <darryl(dot)green(at)gmail(dot)com>
Cc: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Partitioning, Identity and Uniqueness (given pg 16 changes)
Date: 2024-02-22 18:33:00
Message-ID: CAKAnmmJnHn8Z+E=+-XqZi6J=AV9-RTto4e3tc0RvMXbkq1Zmrg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Browse pgsql-general by date

  From Date Subject
Next Message yudhi s 2024-02-22 20:35:10 Creating table and indexes for new application
Previous Message Moreno Andreo 2024-02-22 17:25:42 Re: [SPAM] Re: Partial table duplication via triggger