Do you plan to implement the possibility of excluding tablespaces (TS) from the backup?
Explanation: Since a DBMS can have a large volume of > 5 TB, we often create partitions by year, in a separate tablespace,
after the data is filled in and does not change further, access to the tablespaces becomes READ only. In order not to process them, we exclude them from backup.
In my opinion, this is a very necessary feature for those organizations that use large databases.
[feature request]
-
- Lurker
- Posts: 2
- Liked: 1 time
- Joined: May 31, 2023 12:57 pm
- Full Name: Alexander
- Location: MINSK
- Contact:
-
- Veeam Software
- Posts: 3681
- Liked: 620 times
- Joined: Aug 28, 2013 8:23 am
- Full Name: Petr Makarov
- Location: Prague, Czech Republic
- Contact:
Re: Exclusion TABLESPACE in PostgreSQL [feature request].
Hi Alexander,
The request is noted. Any chance to use file-level exclusions as a workaround?
Thanks!
The request is noted. Any chance to use file-level exclusions as a workaround?
Thanks!
-
- Lurker
- Posts: 2
- Liked: 1 time
- Joined: May 31, 2023 12:57 pm
- Full Name: Alexander
- Location: MINSK
- Contact:
Re: Exclusion TABLESPACE in PostgreSQL [feature request].
Thank you. A workaround can be used. Of course, the postgres community needs revision.
Who is online
Users browsing this forum: Majestic-12 [Bot], Mildur and 100 guests