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 16:28:15
Message-ID: 6e0e57e5-ace5-4d18-b1c1-7a3b3da36316@dunslane.net
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers


On 2025-04-14 Mo 8:20 AM, Álvaro Herrera wrote:
> On 2025-Apr-04, Andrew Dunstan wrote:
>
>> Non text modes for pg_dumpall, correspondingly change pg_restore
> I think the new oid_string_list stuff in this commit is unnecessary, and
> we can remove a bunch of lines by simplifying that to using
> SimplePtrList, as the attached illustrates. (Perhaps the names of
> members of the proposed struct can be improved.)

Sure, we can do it that way.

>
> I also propose to remove the open-coded implementation of pg_get_line.
>
> WDYT?

seems reasonable

>
> 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.

cheers

andrew

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

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Andrew Dunstan 2025-04-14 20:14:37 Re: pgsql: Non text modes for pg_dumpall, correspondingly change pg_restore
Previous Message Andres Freund 2025-04-14 14:13:27 Re: pgsql: Add function to get memory context stats for processes

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2025-04-14 16:31:22 Re: Add estimated hit ratio to Memoize in EXPLAIN to explain cost adjustment
Previous Message Jacob Champion 2025-04-14 16:12:53 Re: [PoC] Federated Authn/z with OAUTHBEARER