Re: pg_restore V12 fails consistently against piped pg_dumps

From: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>
To: Mohamed Wael Khobalatte <mkhobalatte(at)grubhub(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: pg_restore V12 fails consistently against piped pg_dumps
Date: 2020-05-08 06:47:20
Message-ID: 9229bd9315ae87f8184872ec13d9d988bde95be1.camel@cybertec.at
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, 2020-05-07 at 11:04 -0400, Mohamed Wael Khobalatte wrote:
> Thanks Tom, I will review those changes tonight. In the meantime, to
> reproduce, I run the following:
>
> - createdb test
> - create some tables, I used a simple loop to create 10 empty ones.
> - pg_dump -v -Fc test | tee test.dump > /dev/null (so it's through a
> pipe, same as if the file is streamed through curl which was the
> original case)
> - pg_restore -j4 --verbose --clean --no-acl --no-owner -d test test.dump
>
> That should fail consistently. pg_restore_12 and pg_dump_12. Same
> passes in if I run in earlier versions.

I just tried that and didn't encounter any errors.

Please come up with a more complete example.

Are you OS user "postgres" when you run that?

Yours,
Laurenz Albe
--
Cybertec | https://www.cybertec-postgresql.com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Jill Jade 2020-05-08 07:32:21 Re: pg_temp schema created while using DB Link
Previous Message Laurenz Albe 2020-05-08 06:41:48 Re: Odd postgres12 upgrade is changing or munging a password?