Re: identify partitioning columns and best practices of partitioning in prod enviornments

From: Ron <ronljohnsonjr(at)gmail(dot)com>
To: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: identify partitioning columns and best practices of partitioning in prod enviornments
Date: 2020-11-11 22:58:00
Message-ID: 921baf8a-195b-fb45-292f-2618f5088302@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 11/11/20 4:31 PM, Atul Kumar wrote:
> Hi,
>
> I want to about best practices of partitioning in prod environments
> and how to identify partitioning columns.

It depends on what you want to do.  If your purpose is to simplify the
deletion of old records, then partition by an unchanging date field.
If your purpose is to increase locality of data (because many of your
queries are an equality on a specific "group id"), then partition by that
"group id" field.

--
Angular momentum makes the world go 'round.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Michael Lewis 2020-11-11 23:47:02 Re: identify partitioning columns and best practices of partitioning in prod enviornments
Previous Message Atul Kumar 2020-11-11 22:31:27 identify partitioning columns and best practices of partitioning in prod enviornments