Re: identify partitioning columns and best practices of partitioning in prod enviornments - Mailing list pgsql-general

From Ron
Subject Re: identify partitioning columns and best practices of partitioning in prod enviornments
Date
Msg-id 921baf8a-195b-fb45-292f-2618f5088302@gmail.com
Whole thread Raw
In response to identify partitioning columns and best practices of partitioning in prod enviornments  (Atul Kumar <akumar14871@gmail.com>)
Responses Re: identify partitioning columns and best practices of partitioning in prod enviornments  (Michael Lewis <mlewis@entrata.com>)
List 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.



pgsql-general by date:

Previous
From: Atul Kumar
Date:
Subject: identify partitioning columns and best practices of partitioning in prod enviornments
Next
From: Michael Lewis
Date:
Subject: Re: identify partitioning columns and best practices of partitioning in prod enviornments