public inbox for pgsql-general@postgresql.org
help / color / mirror / Atom feedRe: Tablespace size in TB
13+ messages / 8 participants
[nested] [flat]
* Re: Tablespace size in TB
@ 2026-05-03 12:47 Jan Karremans <karremans.ja@gmail.com>
0 siblings, 2 replies; 13+ messages in thread
From: Jan Karremans @ 2026-05-03 12:47 UTC (permalink / raw)
To: masheed ullah <masheedullah@gmail.com>; +Cc: Laurenz Albe <laurenz.albe@cybertec.at>; Thiemo Kellner <thiemo@gelassene-pferde.biz>; pgsql-general@lists.postgresql.org
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:
>
> 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.ja@gmail.com <mailto:karremans.ja@gmail.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.albe@cybertec.at <mailto:laurenz.albe@cybertec.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
>
>
^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: Tablespace size in TB
@ 2026-05-03 15:54 Greg Hennessy <greg.hennessy@gmail.com>
parent: Jan Karremans <karremans.ja@gmail.com>
1 sibling, 2 replies; 13+ messages in thread
From: Greg Hennessy @ 2026-05-03 15:54 UTC (permalink / raw)
To: Jan Karremans <karremans.ja@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
--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 <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 <karremans.ja@gmail.com> 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 <masheedullah@gmail=
.com> 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 backup time t=
o less than 10hours.<div><br> 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 <<a href=3D"mailto:karremans.=
ja@gmail.com">karremans.ja@gmail.com</a>> 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>
> On 3 May 2026, at 14:21, Laurenz Albe <<a href=3D"mailto:laurenz.alb=
e@cybertec.at" target=3D"_blank">laurenz.albe@cybertec.at</a>> wrote:<br>=
> <br>
> On Sun, 2026-05-03 at 14:10 +0200, Jan Karremans wrote:<br>
>> Contrary to Oracle, a table space in PostgreSQL is a directory. And=
not a logical abstraction.<br>
>> Moving tables from one table space to another becomes so much easie=
r by that.<br>
> <br>
> I am confused. Yes, if you have more than a single (default) tabl=
espace,<br>
> moving tables between tablespaces becomes possible and hence easier.<br=
>
> But why would you want to move tables between tablespaces in the first p=
lace?<br>
> <br>
> Yours,<br>
> 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--
^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: Tablespace size in TB
@ 2026-05-03 17:07 Christophe Pettus <xof@thebuild.com>
parent: Greg Hennessy <greg.hennessy@gmail.com>
1 sibling, 0 replies; 13+ messages in thread
From: Christophe Pettus @ 2026-05-03 17:07 UTC (permalink / raw)
To: Greg Hennessy <greg.hennessy@gmail.com>; +Cc: Jan Karremans <karremans.ja@gmail.com>; masheed ullah <masheedullah@gmail.com>; Laurenz Albe <laurenz.albe@cybertec.at>; Thiemo Kellner <thiemo@gelassene-pferde.biz>; pgsql-general@lists.postgresql.org
> On May 3, 2026, at 08:54, Greg Hennessy <greg.hennessy@gmail.com> wrote:
>
> Is the fact that other companies are taking
> Over support for pgBackRest documented?
Just speaking for my company:
https://github.com/pgexperts/pgxbackup
^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: Tablespace size in TB
@ 2026-05-04 05:55 Ilya Kosmodemiansky <ik@dataegret.com>
parent: Greg Hennessy <greg.hennessy@gmail.com>
1 sibling, 1 reply; 13+ messages in thread
From: Ilya Kosmodemiansky @ 2026-05-04 05:55 UTC (permalink / raw)
To: Greg Hennessy <greg.hennessy@gmail.com>; +Cc: Jan Karremans <karremans.ja@gmail.com>; masheed ullah <masheedullah@gmail.com>; Laurenz Albe <laurenz.albe@cybertec.at>; Thiemo Kellner <thiemo@gelassene-pferde.biz>; pgsql-general@lists.postgresql.org
Hi Greg,
On Sun, May 3, 2026 at 5:55 PM Greg Hennessy <greg.hennessy@gmail.com>
wrote:
> Is the fact that other companies are taking
> Over support for pgBackRest documented?
>
Making a company-branded fork is the easiest (and wrong) step. Planning how
to pick up the pgBackRest project or create a sustainable, community-driven
fork that re-establishes at least the same reputation requires longer
preparation. We all need patience.
>
>
--
Ilya Kosmodemiansky
CEO, Founder
Data Egret GmbH
Your remote PostgreSQL DBA team
T.: +49 6821 919 3297
ik@dataegret.com
^ permalink raw reply [nested|flat] 13+ messages in thread
* pgBackRest maintenance (was Re: Tablespace size in TB)
@ 2026-05-04 06:45 Christophe Pettus <xof@thebuild.com>
parent: Ilya Kosmodemiansky <ik@dataegret.com>
0 siblings, 1 reply; 13+ messages in thread
From: Christophe Pettus @ 2026-05-04 06:45 UTC (permalink / raw)
To: pgsql-general@lists.postgresql.org
> On May 3, 2026, at 22:55, Ilya Kosmodemiansky <ik@dataegret.com> wrote:
> Making a company-branded fork is the easiest (and wrong) step. Planning how to pick up the pgBackRest project or create a sustainable, community-driven fork that re-establishes at least the same reputation requires longer preparation. We all need patience.
Dave was quite clear that someone "picking up the pgBackRest project" was not on the table. I don't think that avenue is open.
I would feel more sanguine about the idea that a new community-suported fork will emerge if there were an existence proof of it happening in the PostgreSQL community. I can't think of one.
We need to tell our customers something, and "the community will ride in and maintain pgBackRest, just you wait" isn't a satisfactory answer. We can tell clients all we want that the current pgBackRest version works just fine, they don't have to change, a community standard version will emerge, and so forth, but that falls on deaf ears. This is a backup tool; it's second only to PostgreSQL itself in the "must work all the time" camp. All they hear is what it says on the repo, which is "pgBackRest is no longer being maintained."
I think it more likely that an entirely new backup tool will emerge, become the de facto community standards, and then we will move off pgBackRest (and its forks) onto that.
^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: Tablespace size in TB
@ 2026-05-12 05:40 Frank Lanitz <frank@frank.uvena.de>
parent: Jan Karremans <karremans.ja@gmail.com>
1 sibling, 0 replies; 13+ messages in thread
From: Frank Lanitz @ 2026-05-12 05:40 UTC (permalink / raw)
To: pgsql-general@lists.postgresql.org
On 5/3/26 2:47 PM, Jan Karremans wrote:
> You can safely recommend pgBackRest as several PostgreSQL companies have already stepped up to take over/fork pgBackRest.
And ensure the customer is supporting developing / maintaining affords.
What's free cannot be good, isn't it? ;)
.f
^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: pgBackRest maintenance (was Re: Tablespace size in TB)
@ 2026-05-14 17:26 Bruce Momjian <bruce@momjian.us>
parent: Christophe Pettus <xof@thebuild.com>
0 siblings, 1 reply; 13+ messages in thread
From: Bruce Momjian @ 2026-05-14 17:26 UTC (permalink / raw)
To: Christophe Pettus <xof@thebuild.com>; +Cc: pgsql-general@lists.postgresql.org; Peter Eisentraut <peter@eisentraut.org>
On Sun, May 3, 2026 at 11:45:53PM -0700, Christophe Pettus wrote:
>
>
> > On May 3, 2026, at 22:55, Ilya Kosmodemiansky <ik@dataegret.com>
> > wrote: Making a company-branded fork is the easiest (and wrong)
> > step. Planning how to pick up the pgBackRest project or create a
> > sustainable, community-driven fork that re-establishes at least the
> > same reputation requires longer preparation. We all need patience.
>
> Dave was quite clear that someone "picking up the pgBackRest project"
> was not on the table. I don't think that avenue is open.
>
> I would feel more sanguine about the idea that a new
> community-sported fork will emerge if there were an existence proof
> of it happening in the PostgreSQL community. I can't think of one.
That happened with pgbouncer where development stopped and a new team
picked it up. I think Peter Eisentraut was involved. With pgbackrest,
I think a similar thing would need to happen, but with a new name.
--
Bruce Momjian <bruce@momjian.us> https://momjian.us
EDB https://enterprisedb.com
Do not let urgent matters crowd out time for investment in the future.
^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: pgBackRest maintenance (was Re: Tablespace size in TB)
@ 2026-05-14 17:54 Josef Šimánek <josef.simanek@gmail.com>
parent: Bruce Momjian <bruce@momjian.us>
0 siblings, 2 replies; 13+ messages in thread
From: Josef Šimánek @ 2026-05-14 17:54 UTC (permalink / raw)
To: Bruce Momjian <bruce@momjian.us>; +Cc: Christophe Pettus <xof@thebuild.com>; pgsql-general@lists.postgresql.org; Peter Eisentraut <peter@eisentraut.org>
čt 14. 5. 2026 v 19:26 odesílatel Bruce Momjian <bruce@momjian.us> napsal:
>
> On Sun, May 3, 2026 at 11:45:53PM -0700, Christophe Pettus wrote:
> >
> >
> > > On May 3, 2026, at 22:55, Ilya Kosmodemiansky <ik@dataegret.com>
> > > wrote: Making a company-branded fork is the easiest (and wrong)
> > > step. Planning how to pick up the pgBackRest project or create a
> > > sustainable, community-driven fork that re-establishes at least the
> > > same reputation requires longer preparation. We all need patience.
> >
> > Dave was quite clear that someone "picking up the pgBackRest project"
> > was not on the table. I don't think that avenue is open.
> >
> > I would feel more sanguine about the idea that a new
> > community-sported fork will emerge if there were an existence proof
> > of it happening in the PostgreSQL community. I can't think of one.
>
> That happened with pgbouncer where development stopped and a new team
> picked it up. I think Peter Eisentraut was involved. With pgbackrest,
> I think a similar thing would need to happen, but with a new name.
I think David is back and no fork is needed currently.
https://github.com/pgbackrest/pgbackrest/commit/b93a2b8807adabec02ef33cca838e30f109c3eba
> --
> Bruce Momjian <bruce@momjian.us> https://momjian.us
> EDB https://enterprisedb.com
>
> Do not let urgent matters crowd out time for investment in the future.
>
>
^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: pgBackRest maintenance (was Re: Tablespace size in TB)
@ 2026-05-14 18:03 Ron Johnson <ronljohnsonjr@gmail.com>
parent: Josef Šimánek <josef.simanek@gmail.com>
1 sibling, 1 reply; 13+ messages in thread
From: Ron Johnson @ 2026-05-14 18:03 UTC (permalink / raw)
To: pgsql-generallists.postgresql.org <pgsql-general@lists.postgresql.org>
On Thu, May 14, 2026 at 1:55 PM Josef Šimánek <josef.simanek@gmail.com>
wrote:
[snip]
> I think David is back and no fork is needed currently.
>
> https://github.com/pgbackrest/pgbackrest/commit/b93a2b8807adabec02ef33cca838e30f109c3eba
xkcd 2347
--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!
^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: pgBackRest maintenance (was Re: Tablespace size in TB)
@ 2026-05-14 18:06 Josef Šimánek <josef.simanek@gmail.com>
parent: Ron Johnson <ronljohnsonjr@gmail.com>
0 siblings, 0 replies; 13+ messages in thread
From: Josef Šimánek @ 2026-05-14 18:06 UTC (permalink / raw)
To: Ron Johnson <ronljohnsonjr@gmail.com>; +Cc: pgsql-generallists.postgresql.org <pgsql-general@lists.postgresql.org>
čt 14. 5. 2026 v 20:04 odesílatel Ron Johnson <ronljohnsonjr@gmail.com> napsal:
>
> On Thu, May 14, 2026 at 1:55 PM Josef Šimánek <josef.simanek@gmail.com> wrote:
> [snip]
>>
>> I think David is back and no fork is needed currently.
>> https://github.com/pgbackrest/pgbackrest/commit/b93a2b8807adabec02ef33cca838e30f109c3eba
>
>
>
> xkcd 2347
quoting from the message
"We should also be able to bring on another maintainer to distribute
the workload and provide continuity in the future." to prevent that
:pray:
>
> --
> Death to <Redacted>, and butter sauce.
> Don't boil me, I'm still alive.
> <Redacted> lobster!
^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: pgBackRest maintenance (was Re: Tablespace size in TB)
@ 2026-05-14 19:56 Bruce Momjian <bruce@momjian.us>
parent: Josef Šimánek <josef.simanek@gmail.com>
1 sibling, 1 reply; 13+ messages in thread
From: Bruce Momjian @ 2026-05-14 19:56 UTC (permalink / raw)
To: Josef Šimánek <josef.simanek@gmail.com>; +Cc: Christophe Pettus <xof@thebuild.com>; pgsql-general@lists.postgresql.org; Peter Eisentraut <peter@eisentraut.org>
On Thu, May 14, 2026 at 07:54:30PM +0200, Josef Šimánek wrote:
> čt 14. 5. 2026 v 19:26 odesílatel Bruce Momjian <bruce@momjian.us> napsal:
> >
> > On Sun, May 3, 2026 at 11:45:53PM -0700, Christophe Pettus wrote:
> > >
> > >
> > > > On May 3, 2026, at 22:55, Ilya Kosmodemiansky <ik@dataegret.com>
> > > > wrote: Making a company-branded fork is the easiest (and wrong)
> > > > step. Planning how to pick up the pgBackRest project or create a
> > > > sustainable, community-driven fork that re-establishes at least the
> > > > same reputation requires longer preparation. We all need patience.
> > >
> > > Dave was quite clear that someone "picking up the pgBackRest project"
> > > was not on the table. I don't think that avenue is open.
> > >
> > > I would feel more sanguine about the idea that a new
> > > community-sported fork will emerge if there were an existence proof
> > > of it happening in the PostgreSQL community. I can't think of one.
> >
> > That happened with pgbouncer where development stopped and a new team
> > picked it up. I think Peter Eisentraut was involved. With pgbackrest,
> > I think a similar thing would need to happen, but with a new name.
>
> I think David is back and no fork is needed currently.
> https://github.com/pgbackrest/pgbackrest/commit/b93a2b8807adabec02ef33cca838e30f109c3eba
Well, the pgbackrest website doesn't say that:
https://pgbackrest.org/
I thought updating that would have been the first thing done if the
status changed.
--
Bruce Momjian <bruce@momjian.us> https://momjian.us
EDB https://enterprisedb.com
Do not let urgent matters crowd out time for investment in the future.
^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: pgBackRest maintenance (was Re: Tablespace size in TB)
@ 2026-05-14 20:10 Josef Šimánek <josef.simanek@gmail.com>
parent: Bruce Momjian <bruce@momjian.us>
0 siblings, 1 reply; 13+ messages in thread
From: Josef Šimánek @ 2026-05-14 20:10 UTC (permalink / raw)
To: Bruce Momjian <bruce@momjian.us>; +Cc: Christophe Pettus <xof@thebuild.com>; pgsql-general@lists.postgresql.org; Peter Eisentraut <peter@eisentraut.org>
čt 14. 5. 2026 v 21:56 odesílatel Bruce Momjian <bruce@momjian.us> napsal:
>
> On Thu, May 14, 2026 at 07:54:30PM +0200, Josef Šimánek wrote:
> > čt 14. 5. 2026 v 19:26 odesílatel Bruce Momjian <bruce@momjian.us> napsal:
> > >
> > > On Sun, May 3, 2026 at 11:45:53PM -0700, Christophe Pettus wrote:
> > > >
> > > >
> > > > > On May 3, 2026, at 22:55, Ilya Kosmodemiansky <ik@dataegret.com>
> > > > > wrote: Making a company-branded fork is the easiest (and wrong)
> > > > > step. Planning how to pick up the pgBackRest project or create a
> > > > > sustainable, community-driven fork that re-establishes at least the
> > > > > same reputation requires longer preparation. We all need patience.
> > > >
> > > > Dave was quite clear that someone "picking up the pgBackRest project"
> > > > was not on the table. I don't think that avenue is open.
> > > >
> > > > I would feel more sanguine about the idea that a new
> > > > community-sported fork will emerge if there were an existence proof
> > > > of it happening in the PostgreSQL community. I can't think of one.
> > >
> > > That happened with pgbouncer where development stopped and a new team
> > > picked it up. I think Peter Eisentraut was involved. With pgbackrest,
> > > I think a similar thing would need to happen, but with a new name.
> >
> > I think David is back and no fork is needed currently.
> > https://github.com/pgbackrest/pgbackrest/commit/b93a2b8807adabec02ef33cca838e30f109c3eba
>
> Well, the pgbackrest website doesn't say that:
>
> https://pgbackrest.org/
>
> I thought updating that would have been the first thing done if the
> status changed.
Website was also updated, but seems not deployed.
https://github.com/pgbackrest/website/commit/5516003b0f19900fe702b8afd1bc70bc16fede43
I have reported.
> --
> Bruce Momjian <bruce@momjian.us> https://momjian.us
> EDB https://enterprisedb.com
>
> Do not let urgent matters crowd out time for investment in the future.
^ permalink raw reply [nested|flat] 13+ messages in thread
* Re: pgBackRest maintenance (was Re: Tablespace size in TB)
@ 2026-05-15 01:09 Josef Šimánek <josef.simanek@gmail.com>
parent: Josef Šimánek <josef.simanek@gmail.com>
0 siblings, 0 replies; 13+ messages in thread
From: Josef Šimánek @ 2026-05-15 01:09 UTC (permalink / raw)
To: Bruce Momjian <bruce@momjian.us>; +Cc: Christophe Pettus <xof@thebuild.com>; pgsql-general@lists.postgresql.org; Peter Eisentraut <peter@eisentraut.org>
čt 14. 5. 2026 v 22:10 odesílatel Josef Šimánek
<josef.simanek@gmail.com> napsal:
>
> čt 14. 5. 2026 v 21:56 odesílatel Bruce Momjian <bruce@momjian.us> napsal:
> >
> > On Thu, May 14, 2026 at 07:54:30PM +0200, Josef Šimánek wrote:
> > > čt 14. 5. 2026 v 19:26 odesílatel Bruce Momjian <bruce@momjian.us> napsal:
> > > >
> > > > On Sun, May 3, 2026 at 11:45:53PM -0700, Christophe Pettus wrote:
> > > > >
> > > > >
> > > > > > On May 3, 2026, at 22:55, Ilya Kosmodemiansky <ik@dataegret.com>
> > > > > > wrote: Making a company-branded fork is the easiest (and wrong)
> > > > > > step. Planning how to pick up the pgBackRest project or create a
> > > > > > sustainable, community-driven fork that re-establishes at least the
> > > > > > same reputation requires longer preparation. We all need patience.
> > > > >
> > > > > Dave was quite clear that someone "picking up the pgBackRest project"
> > > > > was not on the table. I don't think that avenue is open.
> > > > >
> > > > > I would feel more sanguine about the idea that a new
> > > > > community-sported fork will emerge if there were an existence proof
> > > > > of it happening in the PostgreSQL community. I can't think of one.
> > > >
> > > > That happened with pgbouncer where development stopped and a new team
> > > > picked it up. I think Peter Eisentraut was involved. With pgbackrest,
> > > > I think a similar thing would need to happen, but with a new name.
> > >
> > > I think David is back and no fork is needed currently.
> > > https://github.com/pgbackrest/pgbackrest/commit/b93a2b8807adabec02ef33cca838e30f109c3eba
> >
> > Well, the pgbackrest website doesn't say that:
> >
> > https://pgbackrest.org/
> >
> > I thought updating that would have been the first thing done if the
> > status changed.
>
> Website was also updated, but seems not deployed.
> https://github.com/pgbackrest/website/commit/5516003b0f19900fe702b8afd1bc70bc16fede43
> I have reported.
site is updated now https://pgbackrest.org/
> > --
> > Bruce Momjian <bruce@momjian.us> https://momjian.us
> > EDB https://enterprisedb.com
> >
> > Do not let urgent matters crowd out time for investment in the future.
^ permalink raw reply [nested|flat] 13+ messages in thread
end of thread, other threads:[~2026-05-15 01:09 UTC | newest]
Thread overview: 13+ messages (download: mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2026-05-03 12:47 Re: Tablespace size in TB Jan Karremans <karremans.ja@gmail.com>
2026-05-03 15:54 ` Greg Hennessy <greg.hennessy@gmail.com>
2026-05-03 17:07 ` Christophe Pettus <xof@thebuild.com>
2026-05-04 05:55 ` Ilya Kosmodemiansky <ik@dataegret.com>
2026-05-04 06:45 ` pgBackRest maintenance (was Re: Tablespace size in TB) Christophe Pettus <xof@thebuild.com>
2026-05-14 17:26 ` Re: pgBackRest maintenance (was Re: Tablespace size in TB) Bruce Momjian <bruce@momjian.us>
2026-05-14 17:54 ` Re: pgBackRest maintenance (was Re: Tablespace size in TB) Josef Šimánek <josef.simanek@gmail.com>
2026-05-14 18:03 ` Re: pgBackRest maintenance (was Re: Tablespace size in TB) Ron Johnson <ronljohnsonjr@gmail.com>
2026-05-14 18:06 ` Re: pgBackRest maintenance (was Re: Tablespace size in TB) Josef Šimánek <josef.simanek@gmail.com>
2026-05-14 19:56 ` Re: pgBackRest maintenance (was Re: Tablespace size in TB) Bruce Momjian <bruce@momjian.us>
2026-05-14 20:10 ` Re: pgBackRest maintenance (was Re: Tablespace size in TB) Josef Šimánek <josef.simanek@gmail.com>
2026-05-15 01:09 ` Re: pgBackRest maintenance (was Re: Tablespace size in TB) Josef Šimánek <josef.simanek@gmail.com>
2026-05-12 05:40 ` Frank Lanitz <frank@frank.uvena.de>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox