| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | tcassidy(at)mossridge(dot)com(dot)au, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #15602: pg_dump archive items not in correct section order |
| Date: | 2019-01-23 16:44:17 |
| Message-ID: | 201901231644.rh46t3asx75y@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On 2019-Jan-22, PG Bug reporting form wrote:
> When I run pg_dump on a database, it reports the following warning:
>
> pg_dump: [archiver] WARNING: archive items not in correct section order
>
>
> The following SQL script replicates the warning when run on a new instance
> of PostgreSQL 11.1:
It does indeed ... curious.
repairDependencyLoop sees this curious case involving ten objects:
repairing loop: 10 (mv_2 [type 12], _RETURN [type 17] (on mv_2), table1_pkey [type 19], POST-DATA BOUNDARY [type 37], foo [type 23], PRE-DATA BOUNDARY [type 36], _mv_1 [type 25], mv_1 [type 25], mv_1 [type 12], _RETURN [type 17] (on mv_1))
(I just patched it to print the loop objects as attached)
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| Attachment | Content-Type | Size |
|---|---|---|
| dump-sort.patch | text/x-diff | 761 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Patrick Headley | 2019-01-23 18:49:27 | Folder access issues with pgAdmin4 |
| Previous Message | Brad DeJong | 2019-01-23 15:55:58 | postgresql-9.6.11-1-windows-x64.exe VC++ runtime installer |