https://www.kylehailey.com/post/postgres-partition-pains-lockmanager-waits Partitioning can take your production database down https://www.kylehailey.com/post/postgres-partition-conversion-minimal-downtime Basically there are 4 steps: 1 Rename old table 2 Create new table with partitioning 3 Add constraint on old table for it's proposed partition ranges 4 Attach old table as a partition to new partition table Sounds easy right? What about indexes? What about Triggers? And guess what, there are other traps to watch out for! asd <br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Aug 3, 2023 at 12:47 PM Rajesh Kumar <rajeshkumar.dba09@xxxxxxxxx> wrote:<br></div><blockquote class="gmail_quote" style="margin: 0px 0px 0px 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div dir="ltr">Hi friends,<div><br></div><div>I am using Redhat open shift container and Postgres version 15.2. I wish to convert the normal table into a partitioning table. Please help me with the pre-requisite, each and every step to partition. As far as i know, we can create a new partition(parent and child table) and simply insert data from the old table into the new table and drop the old one. Is that all?</div><div><br></div><div>Please provide me detailed answer with detailed steps.</div><div><br></div><div>Thank you</div><font color="#888888"><div>Kumar.</div></font></div> </blockquote></div>
