Re: Non-text mode for pg_dumpall

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Mahendra Singh Thalor <mahi6run(at)gmail(dot)com>, jian he <jian(dot)universality(at)gmail(dot)com>
Cc: tushar <tushar(dot)ahuja(at)enterprisedb(dot)com>, Vaibhav Dalvi <vaibhav(dot)dalvi(at)enterprisedb(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: Non-text mode for pg_dumpall
Date: 2026-01-06 16:33:38
Message-ID: 4050d002-3dee-4ac6-a4d5-6b6e051d4fb8@dunslane.net
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>

On 2026-01-06 Tu 1:26 AM, Mahendra Singh Thalor wrote:
>
>> It's probably harmless, we connect to the databases further down to do actual work. But it's also not nice. The toc.glo seems to have a bunch of extraneous entries of type COMMENT and CONNECT. Why is that? As far as poible this should have output pretty much identical to a plain pg_dumpall.
>>
>>
> If we don't dump those comments in non-text format, then the output of
> "pg_restore -f filename dump_non_text" will not be the same as the
> plain dump of pg_dumpall.
>
> Here, I am attaching an updated patch for the review and testing.
>
> Note: some of the review comments are still not fixed. I am working on
> those and will post an updated patch.

But these cases are not producing anything like identical output.

here is the diff produced by my standard test case. (I have modified the
output to unify the resttrict/unrestrict keys)

cheers

andrew

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

Attachment Content-Type Size
dumpall_diff text/plain 24.6 KB

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jacob Champion 2026-01-06 16:41:54 Re: Periodic authorization expiration checks using GoAway message
Previous Message Jacob Champion 2026-01-06 16:28:39 Re: Make PGOAUTHCAFILE in libpq-oauth work out of debug mode