Regarding PITR's Inability to Restore Data by Table or Database

This topic has been translated from a Chinese forum by GPT and might contain errors.

Original topic: 关于pitr不能按table或database来恢复数据

| username: caiyfc

Requirement Feedback
Please clearly and accurately describe the problem scenario, desired behavior, and background information to facilitate timely follow-up by the product team.
[Problem Scenario Involved in the Requirement]
When using PITR, it is only possible to perform a full restore or restore data to a snapshot by table or database. Incremental data cannot be restored by table or database.
If I want to restore the incremental data of a specific table, I have to first use PITR to perform a full restore to get the latest data of that table, which is somewhat cumbersome.
[Expected Desired Behavior]
When using PITR, it should be possible to specify the database or table and restore the data to a specified point in time.

| username: hey-hoho | Original post link

Strongly support :100:

| username: dba-kit | Original post link

+1, I have the same requirement. Additionally, it would be best if it supports synchronizing to the existing cluster with a different name during the recovery process. Otherwise, for large table recovery, we have to restore to a new cluster first and then re-import and export again.

| username: DBAER | Original post link

Good requirement

| username: WalterWj | Original post link

Good requirement.

| username: 有猫万事足 | Original post link

Strongly support :100:

| username: zhanggame1 | Original post link

Technically not very feasible.

| username: polars | Original post link

Strong demand

| username: jiayou64 | Original post link

Should it be called precise recovery?

| username: MrSylar | Original post link

Requirement +1

| username: h5n1 | Original post link