Re: R: [GENERAL] Slow queries on very big (and partitioned) table - Mailing list pgsql-general

From Rakesh Kumar
Subject Re: R: [GENERAL] Slow queries on very big (and partitioned) table
Date
Msg-id MWHPR2201MB1565299932D564798DDB4ABC8C510@MWHPR2201MB1565.namprd22.prod.outlook.com
Whole thread Raw
In response to R: R: [GENERAL] Slow queries on very big (and partitioned) table  (Job <Job@colliniconsulting.it>)
List pgsql-general
> We thought to implement one partition for day.

That would be 365 partitions in a year.

In our experience INSERTS suffers the most in a partitioned table because triggers are the only way to route the row to
theproper child (inherited) table. 

Question: How is your insert pattern? Do you insert always current date. In that case you can write the trigger code to
havecurrent date at the top so that the insert trigger finds the matching date as early as possible. 

Selects, updates and deletes are reasonably better.

pgsql-general by date:

Previous
From: Job
Date:
Subject: R: R: [GENERAL] Slow queries on very big (and partitioned) table
Next
From: Adrian Klaver
Date:
Subject: Re: [GENERAL] bloat indexes - opinion