| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | David Barron <david(dot)barron(at)zencos(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Backup strategy |
| Date: | 2024-02-28 16:50:53 |
| Message-ID: | CAH2-Wzn5aROAPLQTLa8o1dqMV_KAEkiUPTrDLVPyp9YZjeAKWA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Wed, Feb 28, 2024 at 11:45 AM David Barron <david(dot)barron(at)zencos(dot)com> wrote:
> David Barron <david(dot)barron(at)zencos(dot)com> writes:
> > I'm responsible for a couple of databases that have constraints and indexes on most, if not all, of the tables, which means that the tables have to be backed up and restored in the correct order to take the constraints into account. But pg_dump and pg_restore don't take that into account, so when doing restores I was running into errors.
Are you doing the backups on a physical replica?
I wonder if it could be related to an issue that this user also ran
into a little while ago:
https://postgr.es/m/17846-1a0e5ce976f4c01a@postgresql.org
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2024-02-28 16:52:43 | Re: Backup strategy |
| Previous Message | Tom Lane | 2024-02-28 16:48:54 | Re: Backup strategy |