I dropped the table and recreated the partition table by using the Range by the condition. Regarding performance improvement, I am working on it like creating a separate index for sub-partition also parallel process if it is possible
Thanks & Best Wishes,
Ashok
---------------------------------------------------------------------------------------------------------------------
Ashokkumar Mani (OCP12c/11g/10g/9i, AWS SAA, M103)
Dubai , UAE | BLR , INDIA
M: +971 54 723 0075 | +91 90086 70302 | WApp : +91 81975 99922
W: https://dbatocloudsolution.blogspot.in/
| E: dbatocloud17@xxxxxxxxx
On Wed, Mar 3, 2021 at 4:34 PM Laurenz Albe <laurenz.albe@xxxxxxxxxxx> wrote:
On Wed, 2021-03-03 at 14:31 +0530, dbatoCloud Solution wrote:
> Thanks! I understood the problem, But, at this moment it is not possible to
> upgrade the DB version (10.13) to 11 or 12 due to a sprint issue.
PostgreSQL v10 already has (limited) partitioning support, but I'd
rather use that than inheritance partitioning.
> Is there any other way to improve the performance?
Partitioning typically doesn't improve query performance...
Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com
