Re: Segfault when restoring -Fd dump on current HEAD
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Justin Pryzby <pryzby@telsasoft.com>
Cc: Alvaro Herrera <alvherre@2ndquadrant.com>,
Dmitry Dolgov <9erthalion6@gmail.com>, depesz@depesz.com,
pgsql-hackers mailing list <pgsql-hackers@postgresql.org>
Date: 2019-02-25T16:20:14Z
Lists: pgsql-hackers
Justin Pryzby <pryzby@telsasoft.com> writes: > What's crashing for me is restoring the (12dev) dumpfile using v11 psql: Yeah, I can reproduce that here, using either -Fc or -Fd format dumps. The immediate problem in your example is that the "defn" field of a TABLE DATA entry is now null where it used to be an empty string. Poking at related examples suggests that other fields have suffered the same fate. It appears to me that f831d4acc required a good deal more adult supervision than it actually got. That was alleged to be a small notational refactoring, not a redefinition of what gets put into dump files. regards, tom lane
Commits
-
pg_dump: store unused attribs as NULL instead of '\0'
- 7fcdb5e00214 12.0 landed
-
pg_dump: Fix ArchiveEntry handling of some empty values
- 19455c9f5606 12.0 landed