From: | Rui DeSousa <rui(at)crazybean(dot)net> |
---|---|
To: | richard coleman <rcoleman(dot)ascentgl(at)gmail(dot)com> |
Cc: | Ron <ronljohnsonjr(at)gmail(dot)com>, pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: pg_dump why no indicator of completion |
Date: | 2023-05-01 14:13:21 |
Message-ID: | A65804DE-890B-4709-AAC4-516748687D72@crazybean.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
> On May 1, 2023, at 9:55 AM, richard coleman <rcoleman(dot)ascentgl(at)gmail(dot)com> wrote:
>
> Are you writing that pg_dump is unfit for purpose and that I should be using a commercial backup solution instead?
>
pg_dump is a logical backup. If you need a fast logical backup; then it’s the right tool. To get a fast logical backup use the directory format, multiple threads (jobs), and turn off compression. You shouldn’t have to wait days to get a logical backup; if so, maybe your system is too small and/or disks are too slow.
i.e. pg_dump --format=d --file=prod --compress=0 —jobs=16 prod
However, for database backups a binary solution is best as it is faster and allows for point in time recovery if archiving is enabled.
Relying on logical backups as a backup solution seems like a bad idea.
-rui
From | Date | Subject | |
---|---|---|---|
Next Message | richard coleman | 2023-05-01 14:31:11 | Re: pg_dump why no indicator of completion |
Previous Message | Ron | 2023-05-01 14:07:17 | Re: pg_dump why no indicator of completion |