Horton

Re: Non-text mode for pg_dumpall

Andrew Dunstan <andrew@dunslane.net>

View thread
From: Andrew Dunstan <andrew@dunslane.net>
To: Ranier Vilela <ranier.vf@gmail.com>
Cc: Mahendra Singh Thalor <mahi6run@gmail.com>, Álvaro Herrera <alvherre@alvh.no-ip.org>, jian he <jian.universality@gmail.com>, Srinath Reddy <srinath2133@gmail.com>, pgsql-hackers@lists.postgresql.org
Date: 2025-04-10T23:08:57Z
Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Add non-text output formats to pg_dumpall

  2. Improve pg_dump/pg_dumpall help synopses and terminology

  3. Non text modes for pg_dumpall, correspondingly change pg_restore

  4. Doc: manually break lines in wide UUID examples.

On 2025-04-10 Th 5:45 PM, Ranier Vilela wrote:
>
> Em qui., 10 de abr. de 2025 às 15:58, Andrew Dunstan 
> <andrew@dunslane.net> escreveu:
>
>
>     On 2025-04-10 Th 2:38 PM, Ranier Vilela wrote:
>>
>>
>>
>>         Thanks. I have pushed these now with a few further small tweaks.
>>
>>     Sorry if it is not the right place.
>>     Coverity has another resource leak alert.
>>
>>     trivial patch attached.
>>
>>
>
>
>     Thanks for checking. Pushed.
>
> Andew, I think that the commit wasn't very correct.
> Now the variable *q* is being destroyed inside the loop.
>
> The patch was destroying the variable *q* (stringinfo),
> after the loop while.
>

Yes, you're right. Must be blind. Fixed.


cheers


andrew


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