On the role of database tables

The previous project encountered a slow sql The problem of , It is caused by a large amount of data postgres, In addition to the index, a sub table is added trigger
The general function is to insert into the parent table maintable According to the field of the inserted record (date) Insert sub tables separately subtable_date in
In this way, the sub table is queried subtable_date
But sub tables don't really exist , In addition, even if the sub table is queried, it will still be queried in the target , This is followed by date What is the difference between conditional queries
What's the point of doing this , Will the performance be improved

---

Take the answer ：

You have inserted data into it , I also said that the sub table does not really exist ？
Create a separate table like this , The meaning is that if there are certain scenarios, only the data in the sub table is required , For example, front-end search condition range control , Then it must be faster to check this sub table than the parent table .
in addition , You didn't give the complete structure of the child table and the parent table , Inquire about sql No , The implementation plan is not posted , I didn't explain the complete logic of the trigger , Nor did it make clear all the scenarios related to these two tables , Therefore, it is not possible to make a comprehensive evaluation of this practice for the time being .

---