| From: | Adam Brusselback <adambrusselback(at)gmail(dot)com> |
|---|---|
| To: | "W(dot)P(dot)" <laurentp(at)wp(dot)pl> |
| Cc: | pgsql-general <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Hot backup in PostgreSQL |
| Date: | 2020-10-22 15:13:39 |
| Message-ID: | CAMjNa7eJZaeNewGq6YwVN=qon87hLiHqJgvQQUZ8B5L4=_0jYw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> how to do "hot backup" (copying files) while database running?
As others have shown, there are ways to do this with PG's internal tooling
(pg_basebackup).
However, I would highly recommend you use an external backup tool like
pgbackrest [1] to save yourself the pain of implementing things incorrectly
and ending up with non-viable backups when you need them most. I'm not
affiliated with them at all, but have just used pgbackrest in production
for years now with great results. It takes care of PITR, and manages
backup retention (and associated WAL retention). Those can be a bit of a
pain to do manually otherwise.
Just my $0.02, hope it helps!
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ayub M | 2020-10-22 19:53:59 | postgres materialized view refresh performance |
| Previous Message | Tom Lane | 2020-10-22 14:14:34 | Re: Initplan placed at the righttree or the lefttree of joinnode |