What's the behaviour when pg_resetwal is used to change the WAL segment
size?
This note is worrying to me:
--
While pg_resetwal will set the WAL starting address beyond the latest
existing WAL segment file, some segment size changes can cause previous WAL
file names to be reused. It is recommended
On Fri, 2025-12-19 at 09:26 +0100, Andrew wrote:
> As an oracle dba new to Postgres, I’m used to the concept of context switches
> and latch issues
> with regards to transaction log switches. Does Postgres have a similar
> mechanism with latching
> etc when it switches to a new wal segment that i
As an oracle dba new to Postgres, I’m used to the concept of context switches
and latch issues with regards to transaction log switches. Does Postgres have a
similar mechanism with latching etc when it switches to a new wal segment that
is alleviated when increasing the size of the wal segments?
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
> > --
> >
Adding this to ~/.ssh/config will almost totally eliminate the cost of ssh
authentication:
Host *
ControlMaster auto
#ControlPath /run/user/%i/%L_%r_at_%n:%p
ControlPath ~/.ssh/%L_%r_at_%n:%p
ControlPersist 5m
Pointing ControlPath to /run/user/%i is even faster, but it doesn't alw
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
On 12/17/25 08:10, 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.
How much of that time is network travel?
What are the co
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.
Any reason not to bump it up to 1GB? Or is that overkill?
/Colin
On Wed, 17 Dec 2025 at 16:25, Laur
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,
> totalling approx 230GB. The archiver
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
> approx 230GB. The archiver is
10 matches
Mail list logo
