| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Mahendra Singh Thalor <mahi6run(at)gmail(dot)com>, Vaibhav Dalvi <vaibhav(dot)dalvi(at)enterprisedb(dot)com> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Non-text mode for pg_dumpall |
| Date: | 2025-11-11 15:11:52 |
| Message-ID: | 17555e46-4fb2-4265-90e0-95cb8ed584a6@dunslane.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2025-11-11 Tu 12:59 AM, Mahendra Singh Thalor wrote:
>
> Hi,
> Here, I am attaching an updated patch for the review and testing.
>
> FIX: as suggested by Vaibhav, added error for --restrict-key option
> with non-text format.
>
Regarding the name and format of the globals toc file, I'm inclined to
think we should always use custom format, regardless of whether the
individual databases will be in custom, tar or directory formats, and
that it should be called something distinguishable, e.g. toc.glo.
cheers
andrew
--
Andrew Dunstan
EDB: https://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sugamoto Shinya | 2025-11-11 15:13:49 | Re: [PATCH] Add hints for invalid binary encoding names in encode/decode functions |
| Previous Message | Tom Lane | 2025-11-11 15:04:08 | Re: CURL_IGNORE_DEPRECATION |