Re: BUG #18923: pg_dump 18beta1 fails to process complex table names
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Nathan Bossart <nathandbossart@gmail.com>
Cc: jian he <jian.universality@gmail.com>, phb.emaj@free.fr,
pgsql-bugs@lists.postgresql.org
Date: 2025-05-15T19:03:21Z
Lists: pgsql-bugs
Nathan Bossart <nathandbossart@gmail.com> writes: > I don't think we want to teach appendPGArray() to handle single quotes. No, that seems quite wrong. array_in won't de-dup single quotes. > My first instinct is that we need to build the array with appendPGArray() > and then append it to the query using appendStringLiteralAH(), as done in > the attached patch. Yeah, I think so. I was confused for a bit because the one extant user of appendPGArray is getNamespaces which does an additional layer of quote-doubling via quoteAclUserName. However, that seems to be because it's trying to build aclitem[] arrays whose elements will be read by aclitemin, and that de-dups double quotes. Wouldn't be a bad idea to add a test case. regards, tom lane
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
pg_dump: Fix array literals in fetchAttributeStats().
- a6060f1cbec3 18.0 landed