Re: Fix pg_restore --no-globals SQL output for pg_dumpall archives - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: Fix pg_restore --no-globals SQL output for pg_dumpall archives
Date
Msg-id 3a35a5cb-c4b4-4224-b342-638dcd98c41d@dunslane.net
Whole thread
In response to Re: Fix pg_restore --no-globals SQL output for pg_dumpall archives  (Chao Li <li.evan.chao@gmail.com>)
List pgsql-hackers
On 2026-06-17 We 10:56 PM, Chao Li wrote:
>
>> On Jun 17, 2026, at 22:43, Andrew Dunstan <andrew@dunslane.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
optionto 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?


Yes, see https://postgr.es/m/20260607000218.96.noahmisch@microsoft.com


cheers


andrew

--
Andrew Dunstan
EDB: https://www.enterprisedb.com




pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: fix pg_mkdir_p to tolerate concurrent directory creation
Next
From: Matthias van de Meent
Date:
Subject: Re: Commit Sequence Numbers and Visibility