Re: Tablespace size in TB

You can safely recommend pgBackRest as several PostgreSQL companies have already stepped up to take over/fork pgBackRest.

> On 3 May 2026, at 14:30, masheed ullah <masheedullah(at)gmail(dot)com> wrote:
>
> The issue is, 13tb database BARMAN backup is taking 20 hours and restore takes 24 hours.
> So the main agenda is to reduce the backup time to less than 10hours.
>
> So does any solution/ tool I recommend to client.
>
> . I just checked pgBeckRest has no more support, so I can not suggest it to client.
>
> On Sun, May 3, 2026 at 3:25 PM Jan Karremans <karremans(dot)ja(at)gmail(dot)com <mailto:karremans(dot)ja(at)gmail(dot)com>> wrote:
>> My thinking would be to have the different directories on different tiers of storage.
>>
>> Cheers,
>> Jan
>>
>> > On 3 May 2026, at 14:21, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at <mailto:laurenz(dot)albe(at)cybertec(dot)at>> wrote:
>> >
>> > On Sun, 2026-05-03 at 14:10 +0200, Jan Karremans wrote:
>> >> Contrary to Oracle, a table space in PostgreSQL is a directory. And not a logical abstraction.
>> >> Moving tables from one table space to another becomes so much easier by that.
>> >
>> > I am confused. Yes, if you have more than a single (default) tablespace,
>> > moving tables between tablespaces becomes possible and hence easier.
>> > But why would you want to move tables between tablespaces in the first place?
>> >
>> > Yours,
>> > Laurenz Albe
>>
>
>
>
> --
> Best Regards,
> Masheed Ullah
>
>