Re: pg_restore --format= option(without any value) should report an error as pg_dump is reporting an error - Mailing list pgsql-hackers

From Mahendra Singh Thalor
Subject Re: pg_restore --format= option(without any value) should report an error as pg_dump is reporting an error
Date
Msg-id CAKYtNArLWuWqmrM05PKJcmeM1UPjcjtEZ=d82SnQSfMF-OXkkA@mail.gmail.com
Whole thread
In response to Re: pg_restore --format= option(without any value) should report an error as pg_dump is reporting an error  (Mahendra Singh Thalor <mahi6run@gmail.com>)
List pgsql-hackers
On Fri, 20 Mar 2026 at 01:31, Mahendra Singh Thalor <mahi6run@gmail.com> wrote:
>
> Thanks Nathan for committing this.
>
> Thanks and Regards
> Mahendra Singh Thalor
> EnterpriseDB: http://www.enterprisedb.com
>
>
> On Thu, 19 Mar 2026 at 12:54 AM, Nathan Bossart <nathandbossart@gmail.com> wrote:
>>
>> Committed.
>>
>> --
>> nathan

Hi Nathan,

This fix was committed as ec80215c033, but it got reverted along with
7ca548f23a6 (the revert of pg_dumpall's non-text output format support) as
collateral damage: the option-parsing block it touched had been restructured
by that feature, so the revert took this change down with it even though it
has nothing to do with non-text formats.

Re-attaching the same fix, unchanged, rebased on the current master.
We can back-port till v19.

--
Thanks and Regards
Mahendra Singh Thalor
EnterpriseDB: http://www.enterprisedb.com

Attachment

pgsql-hackers by date:

Previous
From: Daniel Gustafsson
Date:
Subject: Re: blkreftable.c needs more sanity checks
Next
From: "Jonathan Gonzalez V."
Date:
Subject: Re: pg_plan_advice: add NO_ scan and join method tags