It looks like there is a whole bunch of problems here:
- Bill Tihen's original post about restoring over sockets
- sailor's post about "out-of-order restore request" failure
- David Zhang's crash inside of GSS
I was running into the "out-of-order restore request" issue. My post
above was the first half of my investigations and was incorrect. The
"out-of-order restore request" comes from custom dumps who were
written to a non-seekable file descriptor. They silently lack certain
metadata and can't be used for parallel restores in PostgreSQL 12 or
later. If you're running into "out-of-order restore request" errors
try running pg_dump with the -f flag to force it to create a dump file
with the correct metadata. If you can't change how the dumps are made
you can't use parallel pg_restore with them. There's isn't a code fix
to this problem, everything is working as expected, but I've sent in a
patch to help document the behavior.
https://www.postgresql.org/message-id/CALBH9DDuJ%2BscZc4MEvw5uO-%3DvRyR2%3DQF9%2BYh%3D3hPEnKHWfS81A%40mail.gmail.com
On Mon, May 18, 2020 at 10:04 PM Justin Pryzby <pryzby@telsasoft.com> wrote:
>
> On Thu, Mar 05, 2020 at 07:53:35PM -0800, David Zhang wrote:
> > I can reproduce this pg_restore crash issue (pg_dump crash too when running
> > with multiple jobs) on MacOS 10.14 Mojave and MacOS 10.15 Catalina using
> > following steps.
>
> Isn't this the same as here?
> https://www.postgresql.org/message-id/flat/16041-b44f9931ad91fc3d%40postgresql.org
> ..concluding that macos library fails after forking.
>
> ..I found that via: https://github.com/PostgresApp/PostgresApp/issues/538
> => https://www.postgresql.org/message-id/1575881854624-0.post%40n3.nabble.com
>
> --
> Justin
>
>
--
David Gilman
:DG<
