Re: Non-text mode for pg_dumpall
| От | Andrew Dunstan |
|---|---|
| Тема | Re: Non-text mode for pg_dumpall |
| Дата | |
| Msg-id | 4050d002-3dee-4ac6-a4d5-6b6e051d4fb8@dunslane.net обсуждение исходный текст |
| Ответ на | Re: Non-text mode for pg_dumpall (Mahendra Singh Thalor <mahi6run@gmail.com>) |
| Список | 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.gloseems to have a bunch of extraneous entries of type COMMENT and CONNECT. Why is that? As far as poible this shouldhave 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
Вложения
В списке pgsql-hackers по дате отправления: