Re: Warn when parallel restoring a custom dump without data offsets

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: David Gilman <dgilman(at)gilslotd(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Warn when parallel restoring a custom dump without data offsets
Date: 2020-07-02 21:25:21
Message-ID: 888847.1593725121@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

David Gilman <dgilman(at)gilslotd(dot)com> writes:
> I've attached the latest patches after further review from Justin Pryzby.

I guess I'm completely confused about the purpose of these patches.
Far from coping with the situation of an unseekable file, they appear
to change pg_restore so that it fails altogether if it can't seek
its input file. Why would we want to do this?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Joe Conway 2020-07-02 21:30:49 Re: pg_read_file() with virtual files returns empty string
Previous Message Tom Lane 2020-07-02 20:27:13 Re: pg_read_file() with virtual files returns empty string