From: | Mohamed Wael Khobalatte <mkhobalatte(at)grubhub(dot)com> |
---|---|
To: | 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-07 15:04:30 |
Message-ID: | CABZeWdxxqYiNtkPeZnWfBZ2L_oQvni3qkyjcq8LaL-Om46UA2Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thu, May 7, 2020 at 2:35 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Without a concrete example it's hard to say, but maybe the issue is that
> v12 is more aggressive about parallelizing restores --- see 548e50976.
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.
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2020-05-07 15:14:24 | Re: Lock Postgres account after X number of failed logins? |
Previous Message | Adrian Klaver | 2020-05-07 14:40:11 | Re: Explain plan changes - IN CLAUSE ( Passing direct values Vs INNER Query ) |