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

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Chao Li <li(dot)evan(dot)chao(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Cc: Mahendra Singh Thalor <mahi6run(at)gmail(dot)com>
Subject: Re: Fix pg_restore --no-globals SQL output for pg_dumpall archives
Date: 2026-06-17 14:43:50
Message-ID: 00289eaa-3253-4012-aa91-a0cb8ba8ae19@dunslane.net
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2026-06-17 15:05:30 Re: [PATCH] Fix segmentation fault and infinite loop in jsonb_{plperl,plpython}
Previous Message Nathan Bossart 2026-06-17 14:39:18 Re: PG19beta1: GCC 16.1.1 warning: ‘actual_arg_types’ may be used uninitialized in clauses.c