Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1ts8oA-00FohD-97 for pgsql-hackers@arkaria.postgresql.org; Tue, 11 Mar 2025 23:14:46 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1ts8o9-009ADf-19 for pgsql-hackers@arkaria.postgresql.org; Tue, 11 Mar 2025 23:14:45 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1ts8o8-009ACK-N0 for pgsql-hackers@lists.postgresql.org; Tue, 11 Mar 2025 23:14:44 +0000 Received: from mail-pj1-x102d.google.com ([2607:f8b0:4864:20::102d]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1ts8o6-002JRI-2o for pgsql-hackers@lists.postgresql.org; Tue, 11 Mar 2025 23:14:43 +0000 Received: by mail-pj1-x102d.google.com with SMTP id 98e67ed59e1d1-2ff694d2d4dso8866156a91.0 for ; Tue, 11 Mar 2025 16:14:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1741734882; x=1742339682; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=ZYTQu3hEhMw+00Q2QPfuIEVR75eP0an1Lo23rWQhE7c=; b=Bu1ajMIndWrGha377pJuXD7GjEgKteUiTq+qn/QrmLXV9rcff0PGmHPm0q/+fg10Oy cjrTNFmFiSErDQSDAST5xmDOdIkl//Ni9QEIHHTu4f0JCXdVeXWyBs4L9M7ITEUeZ1AJ yBfLWMb5KA0kzoaDhDV/MSmUo3m1F9ziMj2M0ZglrYCpKrHOO+nIRGZqhvwJ34T19V3j GaVhGYUAwgYIr9dQwn/yVNvRVoO9k/YqQuFoulDfx3IbZ+9S8WQDoRKCBcXT5Z+d8fej CInqcFP8yuc+FBgdN83U205b9ffjggCb7KWeK7pClXI+Pn/16eKKPeu0LaO6MAzWNBwM K2ow== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1741734882; x=1742339682; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=ZYTQu3hEhMw+00Q2QPfuIEVR75eP0an1Lo23rWQhE7c=; b=XzUDiLKCEwFjhPS1hWbbY/dRm61knYY3PhJr2ZMcOVE+h5GwEpSj2M/vpcGPBmOPfT DUVVLzOWr0CkjVnsotI5AbjYmP9QUGz8jSGWzNM7vyN267dR9hFluBxEI0SgqkopMMpv iSJxLPSiJcrILquEITSLzs90QNxLN/IIwgAY8DAP7fUlg+PxfhPB5G5ot2Nga2Tay7dI dKZn0SSTIx9db4858hMJv9uZd9kDyY5+IWayojhIf3xGk7PCxxcuW6WNMNV87Ss+yz92 qNbq2C0FdAwcf4s1t0y1wFaPHvjHNTGrExj+r4ZurkXoTwHxjx1nufXcya45jxa3K94k TSXQ== X-Forwarded-Encrypted: i=1; AJvYcCUS6hDYWcVygvSv6Da3jo19nx6xqwEkiUbsG+mCx5RPGEoh+S96RbveTvheJ3j4VmWbohpYU4LmUGkxqEBU@lists.postgresql.org X-Gm-Message-State: AOJu0YzfAPqOdlo4m8h1LYZy7GcykQgwe8B7gAFnRljuYIek2gvi30ro Rdkl8YA3tz3x0sw4PL9mFRrxhqIQOqRbzVMtGVHCx57M6Pe73VeUgKbvg7ulfgRsBDRtcT6z+4G g3Q8BWmdaaeGmsANqoya62ODVna0= X-Gm-Gg: ASbGncuTyWuvMS2XEnOyBsUAjo5+lgS1+MDWGNUtNhmPca/3QqBoLQWnuEx0u+mWHzt qeKeBlTYfhAOpTSRbynLn5v45mmGB2PZXbFAGRZidnLvvhXkAQ9KY/WV4/68XSBOe+xCcmPf5od yxp8dWA2dIpPWZg77Nxe0/t7c+h1A= X-Google-Smtp-Source: AGHT+IFjgVkJACJRO1YPCCsk9YRny+6uIRIoRssII+TgODfuC6wSp4c0TqGF8hktUg1Rha8i2YqVvWjq/aHBVqattNo= X-Received: by 2002:a17:90b:380e:b0:2ff:682b:b759 with SMTP id 98e67ed59e1d1-2ff7ce5805bmr29919912a91.7.1741734881877; Tue, 11 Mar 2025 16:14:41 -0700 (PDT) MIME-Version: 1.0 References: <202503112103.fltgs54vpq6f@alvherre.pgsql> In-Reply-To: From: Isaac Morland Date: Tue, 11 Mar 2025 19:14:30 -0400 X-Gm-Features: AQ5f1JqimCRhUphBTwSKMchJgQ0skRemLZRopXUIg15HVHJcvayfZHUitnWyl0I Message-ID: Subject: Re: Non-text mode for pg_dumpall To: Andrew Dunstan Cc: =?UTF-8?Q?=C3=81lvaro_Herrera?= , =?UTF-8?Q?Dagfinn_Ilmari_Manns=C3=A5ker?= , Mahendra Singh Thalor , jian he , Srinath Reddy , pgsql-hackers@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000ed6559063019401f" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000ed6559063019401f Content-Type: text/plain; charset="UTF-8" On Tue, 11 Mar 2025 at 18:37, Andrew Dunstan wrote: Well, JSON is supposed to be UTF8. What should we do about database > names that are not UTF8? > How can you have a database name that isn't encodeable in UTF-8? At this point I'm pretty sure Unicode has subsumed essentially every character ever mentioned in a standards document. --000000000000ed6559063019401f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Tue, 11 Mar 2025 at 18:37, Andrew Duns= tan <andrew@dunslane.net> = wrote:

<= /div>
Well, JSON is supposed to be UTF8. What should we do about database
names that are not UTF8?

How can you have a database name that isn&= #39;t encodeable in UTF-8? At this point I'm pretty sure Unicode has su= bsumed essentially every character ever mentioned in a standards document.<= /div>
--000000000000ed6559063019401f--