| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Fire Emerald <fire(dot)github(at)gmail(dot)com> |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: How to interpret 'depends on' errors in pg_restore? |
| Date: | 2024-03-28 14:00:06 |
| Message-ID: | 3571436.1711634406@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Fire Emerald <fire(dot)github(at)gmail(dot)com> writes:
> Then i did a pg_restore -d target --verbose -Fc file.dump and saw in the
> output this:
> 5145 0 730750 TABLE subpartitions backends_y2024w03 userA
> ; depends on: 237
> .... and so on ...
That is not an error, it's just verbose display of one of the items
in the dump.
> Nothing was restored.
You would need to show us the actual errors. (Suggestion:
leave off --verbose, it's just clutter.) A guess though is
that the import failed because of foreign key constraints.
--data-only mode is not good at ordering the table loads to
ensure that FK constraints are satisfied on-the-fly.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2024-03-28 14:22:16 | Re: Inquiry on Participating in the Korean Translation Project for PostgreSQL Documentation |
| Previous Message | David G. Johnston | 2024-03-28 13:32:17 | Re: Problems caused by type resolution for the unknown type |