| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | David Barron <david(dot)barron(at)zencos(dot)com> |
| Cc: | Pgsql-admin <pgsql-admin(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Backup strategy |
| Date: | 2024-02-28 16:48:54 |
| Message-ID: | 2318660.1709138934@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
David Barron <david(dot)barron(at)zencos(dot)com> writes:
> If, for example, table a has a constraint that references rows in table b, table b has to be restored first, but pg_dump doesn't take that into account.
Yes it does: it doesn't restore foreign key constraints until after
all the data is loaded. What I suspect is that by "constraint" you
mean some handmade hack like a trigger that looks at other tables.
But without details about what you're doing, it's hard to recommend
solutions.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2024-02-28 16:50:53 | Re: Backup strategy |
| Previous Message | David Barron | 2024-02-28 16:45:08 | RE: Backup strategy |