On Wed, 2025-12-17 at 12:21 -0500, Greg Sabino Mullane wrote:
> On Wed, Dec 17, 2025 at 11:10 AM Colin 't Hart wrote:
> > Thanks Laurenz, that confirms what I was assuming. Archiving is via
> > pgbackrest
> > to a backup server, over SSH. Approx 750ms to archive each segment is crazy
> > --
> >
crazy -- I'll check compression parameters too.
>
> Any reason not to bump it up to 1GB? Or is that overkill?
>
> /Colin
>
> On Wed, 17 Dec 2025 at 16:25, Laurenz Albe
> wrote:
>
>> On Wed, 2025-12-17 at 16:13 +0100, Colin 't Hart wrote:
>> > I see very little
On Wed, Dec 17, 2025 at 11:10 AM Colin 't Hart wrote:
> Thanks Laurenz, that confirms what I was assuming. Archiving is via
> pgbackrest to a backup server, over SSH. Approx 750ms to archive each
> segment is crazy -- I'll check compression parameters too.
>
Switch to archive-async = on. When do
wrote:
> I see very little advice on tuning WAL segment size.
>
> One of my clients has a few datawarehouses at around 8 - 16 TB
>
> On one of the nodes there are approx 15000 WAL segments of 16MB
each, totalling
> approx 230GB. The archiver is archiv
16:25, Laurenz Albe wrote:
> On Wed, 2025-12-17 at 16:13 +0100, Colin 't Hart wrote:
> > I see very little advice on tuning WAL segment size.
> >
> > One of my clients has a few datawarehouses at around 8 - 16 TB
> >
> > On one of the nodes there are approx 1
On Wed, Dec 17, 2025 at 10:13 AM Colin 't Hart wrote:
> Hi,
>
> I see very little advice on tuning WAL segment size.
>
> One of my clients has a few datawarehouses at around 8 - 16 TB
>
> On one of the nodes there are approx 15000 WAL segments of 16MB each,
> totalli
On Wed, 2025-12-17 at 16:13 +0100, Colin 't Hart wrote:
> I see very little advice on tuning WAL segment size.
>
> One of my clients has a few datawarehouses at around 8 - 16 TB
>
> On one of the nodes there are approx 15000 WAL segments of 16MB each,
> totalling
> app
Hi,
I see very little advice on tuning WAL segment size.
One of my clients has a few datawarehouses at around 8 - 16 TB
On one of the nodes there are approx 15000 WAL segments of 16MB each,
totalling approx 230GB. The archiver is archiving approx one per second, so
approx 4 hours to clear
Hi all,
I have a high traffic database, where I'm interested in changing the
wal segment size to a larger value. I haven't found much
documentation about how to change the segment size of an existing
database. The obvious, safe solution would be to create a new
database cluster and d
