Re: getting "shell command argument contains a newline or carriage return:" error with pg_dumpall when db name have new line in double quote - Mailing list pgsql-hackers

From Andrew Dunstan
Subject Re: getting "shell command argument contains a newline or carriage return:" error with pg_dumpall when db name have new line in double quote
Date
Msg-id 2a6b1449-79f0-4ac2-8fa9-c5986f8d11d9@dunslane.net
Whole thread Raw
In response to Re: getting "shell command argument contains a newline or carriage return:" error with pg_dumpall when db name have new line in double quote  (Nathan Bossart <nathandbossart@gmail.com>)
List pgsql-hackers
On 2026-02-23 Mo 4:03 PM, Nathan Bossart wrote:
> On Sat, Feb 21, 2026 at 01:16:05PM -0500, Andrew Dunstan wrote:
>> OK, I have squashed these two together and tweaked them a bit. I propose to
>> commit this patch fairly soon.
> koel seems to be unhappy with this one:
>
>     https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=koel&dt=2026-02-23%2020%3A19%3A04
>

Thanks, it's been fixed. (I need to work out why my git hook didn't find 
this.)


cheers


andrew

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




pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: pgsql: libpq: Grease the protocol by default
Next
From: Peter Eisentraut
Date:
Subject: Re: Check for memset_explicit() and explicit_memset()