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

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Mahendra Singh Thalor <mahi6run(at)gmail(dot)com>
Cc: Nathan Bossart <nathandbossart(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: pg_restore --format= option(without any value) should report an error as pg_dump is reporting an error
Date: 2026-07-29 20:31:34
Message-ID: 3A7700B0-0A24-44B8-A5B6-E2BE791150AE@yesql.se
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On 14 Jul 2026, at 14:19, Mahendra Singh Thalor <mahi6run(at)gmail(dot)com> wrote:

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

I agree that this change got accidentally reverted and should be re-applied,
but at this point in the cycle I think it's too late to target 19 and will
apply to master only unless there are objections to this plan.

--
Daniel Gustafsson

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Daniel Gustafsson 2026-07-29 20:40:22 Re: [PATCH v2] Don't stop a `vacuumdb --all` on a connection failure
Previous Message Sami Imseih 2026-07-29 20:21:28 Re: Increase repalloc_array() usage in buffile.c