Content-Type: multipart/alternative; boundary=Apple-Mail-6B828C8B-A7C8-4DBE-BAAA-0ECB3BFE0F92
Content-Transfer-Encoding: 7bit
From: Greg Hennessy <greg.hennessy@gmail.com>
Mime-Version: 1.0 (1.0)
Subject: Re: Tablespace size in TB
Date: Sun, 3 May 2026 11:54:57 -0400
Message-Id: <3166829D-694D-4A44-B7F5-A7D454EB77DD@gmail.com>
References: <81DB47B9-3244-41BA-980D-66AC371C8CA6@gmail.com>
Cc: masheed ullah <masheedullah@gmail.com>,
 Laurenz Albe <laurenz.albe@cybertec.at>,
 Thiemo Kellner <thiemo@gelassene-pferde.biz>,
 pgsql-general@lists.postgresql.org
In-Reply-To: <81DB47B9-3244-41BA-980D-66AC371C8CA6@gmail.com>
To: Jan Karremans <karremans.ja@gmail.com>
Archived-At: <https://www.postgresql.org/message-id/3166829D-694D-4A44-B7F5-A7D454EB77DD%40gmail.com>
Precedence: bulk


--Apple-Mail-6B828C8B-A7C8-4DBE-BAAA-0ECB3BFE0F92
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html class=3D"apple-mail-supports-explicit-dark-mode"><head><meta http-equi=
v=3D"content-type" content=3D"text/html; charset=3Dutf-8"></head><body dir=3D=
"auto">Is the fact that other companies are taking&nbsp;<div>Over support fo=
r pgBackRest documented?</div><div><br></div><div><br id=3D"lineBreakAtBegin=
ningOfSignature"><div dir=3D"ltr">Sent from my iPhone</div><div dir=3D"ltr">=
<br><blockquote type=3D"cite">On May 3, 2026, at 8:48=E2=80=AFAM, Jan Karrem=
ans &lt;karremans.ja@gmail.com&gt; wrote:<br><br></blockquote></div><blockqu=
ote type=3D"cite"><div dir=3D"ltr">=EF=BB=BF<meta http-equiv=3D"content-type=
" content=3D"text/html; charset=3Dutf-8">You can safely recommend pgBackRest=
 as several PostgreSQL companies have already stepped up to take over/fork p=
gBackRest.<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 resto=
re takes 24 hours.<br>So the main agenda is to reduce the&nbsp;backup time t=
o 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 su=
pport, 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, M=
ay 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 cla=
ss=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid r=
gb(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.alb=
e@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 easie=
r by that.<br>
&gt; <br>
&gt; I am confused.&nbsp; Yes, if you have more than a single (default) tabl=
espace,<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 p=
lace?<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_signa=
ture"><div dir=3D"ltr"><div><font face=3D"sans-serif" size=3D"2">Best Regard=
s,</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></div></blockquote></div></body></html>=

--Apple-Mail-6B828C8B-A7C8-4DBE-BAAA-0ECB3BFE0F92--