| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com> |
| 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 13:35:59 |
| Message-ID: | 3a35a5cb-c4b4-4224-b342-638dcd98c41d@dunslane.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2026-06-17 We 10:56 PM, Chao Li wrote:
>
>> 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?
Yes, see https://postgr.es/m/20260607000218.96.noahmisch@microsoft.com
cheers
andrew
--
Andrew Dunstan
EDB: https://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2026-06-18 13:43:09 | Re: Non-text mode for pg_dumpall |
| Previous Message | Andrew Dunstan | 2026-06-18 13:18:37 | fix pg_mkdir_p to tolerate concurrent directory creation |