Large table optimization in PostgreSQL?

Question

PostgreSQL

Hello
In PostgreSQL there is a table where a bunch of data flies.
The tablet has grown, already by 70 gigs , and requests, the DBMS processes very tightly.
Is it possible to configure PostgreSQL so that a new table is created in a month , and the information starts to get there, but when querying, the DBMS knows where the old data is and where the new ones are, and makes a selection from the desired table, or even from two at once.
I read about "Partitioning" , but as I understand it, this option does not suit me. I can’t beat the table by columns, there are only 2 of them , "itemid" and "clock"
Please point to let it be true

Answer 1

Partitioning is exactly what you need. You misunderstood it, it is done not by columns, but by column values. That is, if you store the time of creating a record in clock, then you can split a huge table into tables containing records that have only values ​​with a daily period in clock.

Answer 2

this is most like sharding.

Answer 3

Maybe it makes sense to look towards scalable DBMS like hbase?
It was correctly indicated above that partitioning is essentially a splitting of a table into several, for example, on a monthly basis.

Answer 4

The plate has grown, already by 70 gigs, and requests, the DBMS processes very tightly.

To speed up queries, you need to make indexes and optimize the queries themselves.

Answer 5

70 G for modern DBMS and modern servers is ridiculous.
The table from two fields brakes?
Yes, this cannot be if you have indexes.
Vacuum, I hope, did not guess to turn off?