From: Jan Karremans <karremans.ja@gmail.com>
Message-Id: <81DB47B9-3244-41BA-980D-66AC371C8CA6@gmail.com>
Content-Type: multipart/alternative;
	boundary="Apple-Mail=_A0BB5D59-06A9-42D1-8F8A-6A885CDB6398"
Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3864.400.21\))
Subject: Re: Tablespace size in TB
Date: Sun, 3 May 2026 14:47:56 +0200
In-Reply-To: <CAHr8x_u4FedXmcAznU8FdJ4vyxqGdPfKJdtrVwa5mAh4hzLDQg@mail.gmail.com>
Cc: Laurenz Albe <laurenz.albe@cybertec.at>,
 Thiemo Kellner <thiemo@gelassene-pferde.biz>,
 pgsql-general@lists.postgresql.org
To: masheed ullah <masheedullah@gmail.com>
References: <CAHr8x_tgJh2vb8gyq-kmrbtKstaAYUpmWC3+umwGXhOZYeMxOQ@mail.gmail.com>
 <CDB30DC3-C4C6-4437-93E8-6440E0B03782@gmail.com>
 <ba2496302b3d6ae301b90f442bd22dc63cd285af.camel@cybertec.at>
 <86590390-F0A6-448A-985A-AA7CCC5D9C16@gmail.com>
 <CAHr8x_u4FedXmcAznU8FdJ4vyxqGdPfKJdtrVwa5mAh4hzLDQg@mail.gmail.com>
Archived-At: <https://www.postgresql.org/message-id/81DB47B9-3244-41BA-980D-66AC371C8CA6%40gmail.com>
Precedence: bulk


--Apple-Mail=_A0BB5D59-06A9-42D1-8F8A-6A885CDB6398
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

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@gmail.com> wrote:
>=20
> 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.
>=20
>  So does any solution/ tool I recommend to client.
>=20
> . I just checked pgBeckRest has no more support, so I can not suggest =
it to client.
>=20
> On Sun, May 3, 2026 at 3:25=E2=80=AFPM Jan Karremans =
<karremans.ja@gmail.com <mailto:karremans.ja@gmail.com>> wrote:
>> My thinking would be to have the different directories on different =
tiers of storage.
>>=20
>> Cheers,
>> Jan
>>=20
>> > On 3 May 2026, at 14:21, Laurenz Albe <laurenz.albe@cybertec.at =
<mailto:laurenz.albe@cybertec.at>> wrote:
>> >=20
>> > 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.
>> >=20
>> > 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?
>> >=20
>> > Yours,
>> > Laurenz Albe
>>=20
>=20
>=20
>=20
> --
> Best Regards,=20
> Masheed Ullah=20
>=20
>=20


--Apple-Mail=_A0BB5D59-06A9-42D1-8F8A-6A885CDB6398
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html aria-label=3D"message body"><head><meta http-equiv=3D"content-type" =
content=3D"text/html; charset=3Dutf-8"></head><body =
style=3D"overflow-wrap: break-word; -webkit-nbsp-mode: space; =
line-break: after-white-space;">You can safely recommend pgBackRest as =
several PostgreSQL companies have already stepped up to take over/fork =
pgBackRest.<br id=3D"lineBreakAtBeginningOfMessage"><div><br><blockquote =
type=3D"cite"><div>On 3 May 2026, at 14:30, masheed ullah =
&lt;masheedullah@gmail.com&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div><div dir=3D"ltr">The issue is, =
13tb database BARMAN backup is taking 20 hours and restore takes 24 =
hours.<br>So the main agenda is to reduce the&nbsp;backup time to less =
than 10hours.<div><br>&nbsp;So does any solution/ tool I recommend to =
client.</div><div><br></div><div>. I just checked pgBeckRest has no more =
support, so I can not suggest it to client.</div></div><br><div =
class=3D"gmail_quote gmail_quote_container"><div dir=3D"ltr" =
class=3D"gmail_attr">On Sun, May 3, 2026 at 3:25=E2=80=AFPM Jan =
Karremans &lt;<a =
href=3D"mailto:karremans.ja@gmail.com">karremans.ja@gmail.com</a>&gt; =
wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px =
0px 0px 0.8ex;border-left:1px solid =
rgb(204,204,204);padding-left:1ex">My thinking would be to have the =
different directories on different tiers of storage.<br>
<br>
Cheers,<br>
Jan<br>
<br>
&gt; On 3 May 2026, at 14:21, Laurenz Albe &lt;<a =
href=3D"mailto:laurenz.albe@cybertec.at" =
target=3D"_blank">laurenz.albe@cybertec.at</a>&gt; wrote:<br>
&gt; <br>
&gt; On Sun, 2026-05-03 at 14:10 +0200, Jan Karremans wrote:<br>
&gt;&gt; Contrary to Oracle, a table space in PostgreSQL is a directory. =
And not a logical abstraction.<br>
&gt;&gt; Moving tables from one table space to another becomes so much =
easier by that.<br>
&gt; <br>
&gt; I am confused.&nbsp; Yes, if you have more than a single (default) =
tablespace,<br>
&gt; moving tables between tablespaces becomes possible and hence =
easier.<br>
&gt; But why would you want to move tables between tablespaces in the =
first place?<br>
&gt; <br>
&gt; Yours,<br>
&gt; Laurenz Albe<br>
<br>
</blockquote></div><div><br clear=3D"all"></div><div><br></div><span =
class=3D"gmail_signature_prefix">-- </span><br><div dir=3D"ltr" =
class=3D"gmail_signature"><div dir=3D"ltr"><div><font face=3D"sans-serif" =
size=3D"2">Best Regards,</font><font size=3D"3"> </font><font =
face=3D"sans-serif" size=3D"2"><br>
<b>Masheed <font size=3D"2">Ullah</font></b> <br>
</font><br></div><br></div></div>
</div></blockquote></div><br></body></html>=

--Apple-Mail=_A0BB5D59-06A9-42D1-8F8A-6A885CDB6398--