From: | Lonni J Friedman <netllama(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: pg_restore with -j fails (works without -j option) |
Date: | 2011-08-29 01:57:57 |
Message-ID: | CAP=oouG=E+_oO9=N0FzEZZpTpwuEKXabSAwCeJK7wzDTFnRZUw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Sun, Aug 28, 2011 at 6:56 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> I wrote:
>> Lonni J Friedman <netllama(at)gmail(dot)com> writes:
>>> [ this doesn't work: ]
>>> $ cat 2011-08-25-1314280801-nightly.out | pg_restore -j2 -U lfriedman -v -d nightly
>>> pg_restore: [custom archiver] cannot reopen stdin
>>> pg_restore: *** aborted because of error
>
>> I agree though that that's not a terribly friendly error message.
>> I thought we had some code in there to complain about non-seekable
>> input files, but it looks like we missed a case.
>
> On closer inspection, I think it's just that nobody thought very hard
> about presenting this limitation in a user-friendly fashion. I've
> committed a patch that will make it fail like this:
>
> pg_restore: [custom archiver] parallel restore from stdin is not supported
>
> immediately upon startup.
>
Awesome, thanks!
From | Date | Subject | |
---|---|---|---|
Next Message | Greg Smith | 2011-08-29 03:00:35 | Re: Whether the function exists a in pgsql table or not? |
Previous Message | Tom Lane | 2011-08-29 01:56:40 | Re: pg_restore with -j fails (works without -j option) |