Re: pgsql: Non text modes for pg_dumpall, correspondingly change pg_restore

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Álvaro Herrera <alvherre(at)kurilemu(dot)de>, Mahendra Singh Thalor <mahi6run(at)gmail(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Non text modes for pg_dumpall, correspondingly change pg_restore
Date: 2025-04-14 20:14:37
Message-ID: 17b357f9-7a99-4db2-87aa-a16679b52757@dunslane.net
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers


On 2025-04-14 Mo 12:28 PM, Andrew Dunstan wrote:
>
>
>>
>> I'm also not sure about the double sscanf() business there ... There
>> must be a better way to do this.
>
>
>
> Yes, probably. I'll look into that if you like.
>
>
>

something like this?

cheers

andrew

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

Attachment Content-Type Size
pg_restore-cleanup.patch text/x-patch 1.3 KB

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Mahendra Singh Thalor 2025-04-14 22:55:42 Re: pgsql: Non text modes for pg_dumpall, correspondingly change pg_restore
Previous Message Andrew Dunstan 2025-04-14 16:28:15 Re: pgsql: Non text modes for pg_dumpall, correspondingly change pg_restore

Browse pgsql-hackers by date

  From Date Subject
Next Message Daniel Gustafsson 2025-04-14 20:16:38 Re: Adding support for SSLKEYLOGFILE in the frontend
Previous Message Tom Lane 2025-04-14 20:10:54 Re: bug in stored generated column over domain with constraints.