| From: | Erik Wienhold <ewie(at)ewie(dot)name> |
|---|---|
| To: | richard coleman <rcoleman(dot)ascentgl(at)gmail(dot)com> |
| Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org |
| Subject: | Re: pg_dump why no indicator of completion |
| Date: | 2023-05-02 03:05:39 |
| Message-ID: | 525021224.1417508.1682996739307@office.mailbox.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
> On 02/05/2023 04:42 CEST richard coleman <rcoleman(dot)ascentgl(at)gmail(dot)com> wrote:
>
> I'm glad that I was able to bring you a modicum of joy.
I find this entire thread entertaining.
> Backups have to be on a manual basis for the time being when I can schedule
> enough time away from the users to complete it. Manged a 2.2T database this
> afternoon, it only took about 10 hours with pg_dump in the database format
> running 7 jobs.
Differential/incremental backups with Barman or pgBackRest can cut down on this
time.
> Amazingly, my WAL folder has yet to fill up, I guess I must be doing it wrong.
Of course there's not much WAL activity if you schedule your backup for a time
window with low client activity.
--
Erik
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ian Lawrence Barwick | 2023-05-02 03:14:45 | Re: pg_dump why no indicator of completion |
| Previous Message | richard coleman | 2023-05-02 02:42:29 | Re: pg_dump why no indicator of completion |