| From: | Christoph Moench-Tegeder <cmt(at)burggraben(dot)net> |
|---|---|
| To: | Matthias Apitz <guru(at)unixarea(dot)de> |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pg_basebackup |
| Date: | 2023-11-20 11:45:15 |
| Message-ID: | ZVtGy31-a5ZdHzBE@sciurus.exwg.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
## Matthias Apitz (guru(at)unixarea(dot)de):
> 2023-11-16 20:34:13.538 CET [6250] LOG: terminating walsender process due to replication timeout
Besides "what Lauenz said" (especially about the horribly ooutdated
PostgreSQL version): check IO speed and saturation during backup
and make sure you're not stalling. I've seen this beaviour a few
times, mostly in conjunction with btrfs - using a suitably proven
filesystem usually solved the problem (overloaded hardware can
be a problem, too - but modern systems can take quite a bit more
than in the olden days of spinning rust).
Regards,
Christoph
--
Spare Space.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nick DeCoursin | 2023-11-20 21:38:05 | Re: New addition to the merge sql standard |
| Previous Message | Achilleas Mantzios - cloud | 2023-11-20 10:46:34 | Re: pgBackRest on old installation |