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

Andrew Dunstan <andrew@dunslane.net>

From: Andrew Dunstan <andrew@dunslane.net>
To: Nathan Bossart <nathandbossart@gmail.com>
Cc: Mahendra Singh Thalor <mahi6run@gmail.com>, Álvaro Herrera <alvherre@alvh.no-ip.org>, Tom Lane <tgl@sss.pgh.pa.us>, Srinath Reddy <srinath2133@gmail.com>, pgsql-hackers@lists.postgresql.org
Date: 2026-02-24T15:58:31Z
Lists: 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




Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →
  1. Disallow CR and LF in database, role, and tablespace names

  2. Switch the regression tests of pg_upgrade to use TAP tests