Content-Type: text/plain;
	charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3731.500.231\))
Subject: Re: Partition By Range Without PrimaryKey : Postgresql Version 12.8
 on AWS RDS
From: Scott Ribe <scott_ribe@elevated-dev.com>
In-Reply-To: 
 <VI1PR10MB7671781EA8ADC72B088F1D318D439@VI1PR10MB7671.EURPRD10.PROD.OUTLOOK.COM>
Date: Mon, 22 May 2023 09:15:32 -0600
Cc: "pgsql-admin@lists.postgresql.org" <pgsql-admin@lists.postgresql.org>,
 Matti Linnanvuori <matti.linnanvuori@portalify.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <5F09A2FE-117F-47D4-B78B-25023A02AFB7@elevated-dev.com>
References: 
 <VI1PR10MB76711B1B17D38E3CFF4E73008D439@VI1PR10MB7671.EURPRD10.PROD.OUTLOOK.COM>
 <VI1PR10MB7671180739AB51DF1455A1A48D439@VI1PR10MB7671.EURPRD10.PROD.OUTLOOK.COM>
 <404AADDB-83F9-4A4A-B6D7-E736C278EFDA@portalify.com>
 <VI1PR10MB7671D817E765A2ADFA174CAD8D439@VI1PR10MB7671.EURPRD10.PROD.OUTLOOK.COM>
 <9558F0D3-4B5B-4CE2-A27F-156149E75916@elevated-dev.com>
 <2BE78422-2D94-424F-ACA7-1FBAA62D7F5E@elevated-dev.com>
 <VI1PR10MB7671781EA8ADC72B088F1D318D439@VI1PR10MB7671.EURPRD10.PROD.OUTLOOK.COM>
To: Phani Prathyush Somayajula <phani.somayajula@pragmaticplay.com>
Archived-At: 
 <https://www.postgresql.org/message-id/5F09A2FE-117F-47D4-B78B-25023A02AFB7%40elevated-dev.com>
Precedence: bulk

> On May 22, 2023, at 8:07 AM, Phani Prathyush Somayajula =
<phani.somayajula@pragmaticplay.com> wrote:
>=20
> However, since I was telling other ripple effects, we're trying to =
test creating subpartitions by placedon and partitions by brandid like =
below.
>  The reason being : we'll have to archive or purge the data post 90 =
days.

You could still partition by placedon... Partitioning by brandid is not =
much help with rotating out old data.

Why the change in primary key? In fact, your primary key in that example =
is not guaranteed unique--if I'm reading this correctly there is a =
chance of collision.

What's wrong with partitioning by placedon, with a primary key of =
(betid, placedon)?