Re: Fix pg_restore --no-globals SQL output for pg_dumpall archives

From: Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: PostgreSQL-development <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Mahendra Singh Thalor <mahi6run(at)gmail(dot)com>
Subject: Re: Fix pg_restore --no-globals SQL output for pg_dumpall archives
Date: 2026-06-18 02:56:36
Message-ID: 1B729E07-F156-4BF2-9D97-B2E5DEF60B21@gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> On Jun 17, 2026, at 22:43, Andrew Dunstan <andrew(at)dunslane(dot)net> wrote:
>
>
> On 2026-06-17 We 2:05 AM, Chao Li wrote:
>> Hi,
>>
>> While testing “[763aaa06f] Add non-text output formats to pg_dumpall” and “[3c19983cc] pg_restore: add --no-globals option to skip globals”, I found that 3c19983cc might have introduced a regression in 763aaa06f.
>
> I think the plan is to revert that feature for now :-(
>
> cheers
>
> andrew
>
>
> --
> Andrew Dunstan
> EDB: https://www.enterprisedb.com
>

Are there any more serious issues identified for this feature?

Best regards,
--
Chao Li (Evan)
HighGo Software Co., Ltd.
https://www.highgo.com/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2026-06-18 03:03:42 Re: Rename EXISTS-to-ANY converted subplan to exists_to_any
Previous Message Ayush Tiwari 2026-06-18 02:53:51 [PATCH] Fix two incorrect code comments