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 1qoSBg-001Kog-Bt for pgsql-hackers@arkaria.postgresql.org; Thu, 05 Oct 2023 17:31:00 +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 1qoSBd-00G4Er-TT for pgsql-hackers@arkaria.postgresql.org; Thu, 05 Oct 2023 17:30:58 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1qoSBd-00G4Ei-FS for pgsql-hackers@lists.postgresql.org; Thu, 05 Oct 2023 17:30:58 +0000 Received: from mail-pl1-x634.google.com ([2607:f8b0:4864:20::634]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qoSBb-000CpX-VT for pgsql-hackers@postgresql.org; Thu, 05 Oct 2023 17:30:57 +0000 Received: by mail-pl1-x634.google.com with SMTP id d9443c01a7336-1c6219307b2so8953565ad.1 for ; Thu, 05 Oct 2023 10:30:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=j-davis-com.20230601.gappssmtp.com; s=20230601; t=1696527053; x=1697131853; darn=postgresql.org; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:cc:to:from:subject:message-id:from:to:cc:subject :date:message-id:reply-to; bh=bDdWhbeVfMlq+IiavaAasjrjnvbD94h4CvSjHTJDpNs=; b=3AwmjhtSWski094uvcRMWJV9q31Ii+xrW3bricQLR8+Xh0PYXMsNWrZS//KGHarPlT kDFxdkhvGSP7GT/biej8oUnw5YzqESq5QBaDWEH42NlcCW6hUY0ChlBdaa6dYn9K0G09 nhEb/NYMc5HD00okRk6OyVcToykS8o1wsXxe/VZZHNpjnw/V1OV2SuqmtvYT9MS1nGYd XvjMdNJloI3QISipJgulQl4lDneH5d3GNaqsM8g6L+1aNR9XPlgVFNZeP4CJ5qyFosWV IHAkckYZaP1G768lHJ7M3HMqBzhVxG53lmv54EGZ2/sGddsTJj+u0hJj8Wv+PzGdBwa6 u9Lw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1696527053; x=1697131853; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:cc:to:from:subject:message-id:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=bDdWhbeVfMlq+IiavaAasjrjnvbD94h4CvSjHTJDpNs=; b=loVRFq5i5XtraNIgpXk45ZHYA1vY3ptlI6is4gio86twV4lw1QyrSmOwuXBt1yUdaC Y49Q8+0atsvBIVO1FcRvt2tRpR/K6VzqzDaRuWJFHdYdgmo755AzcN9cxgRRibQcnLer Ax6Rq2b0aPNzh3tcWsILCv3n9gxWpnZCYZ3FAiXIfpBVBrK8Xq5VIu/c9+7NRSV0h6rg 6kNzA6xIggdCLBMsL2rkuVdvNbOlI4aDUSytWiV8CUzxVNHbcWx4nroo9Ubih9/ichZC sN9k5dJSv6sxjgMcjOlvV42vT2Z/I7Nqww8sK2hhn2ICBn6+hpdDKm+Smw5KpjttB/5V ARYA== X-Gm-Message-State: AOJu0YyXAz4E+qGXG1GNjk5XOH7aNpns1WbHqdj/kmYAxb38GPQ6/qZq /yyQILWdL7dmz8jtyM1J411/RA== X-Google-Smtp-Source: AGHT+IHgCBFYHKdjMoyXSauKlXe/5WfyAlcrUgWZROnP58QS1KKiwlk5vw6lltcton8+BagST28vYg== X-Received: by 2002:a17:902:7246:b0:1c5:6157:f068 with SMTP id c6-20020a170902724600b001c56157f068mr4807710pll.69.1696527053597; Thu, 05 Oct 2023 10:30:53 -0700 (PDT) Received: from [172.18.10.34] ([12.126.244.130]) by smtp.gmail.com with ESMTPSA id f11-20020a17090274cb00b001bb1f0605b2sm1975784plt.214.2023.10.05.10.30.52 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 05 Oct 2023 10:30:53 -0700 (PDT) Message-ID: Subject: Re: Pre-proposal: unicode normalized text From: Jeff Davis To: Robert Haas , Isaac Morland Cc: Chapman Flack , Nico Williams , pgsql-hackers@postgresql.org Date: Thu, 05 Oct 2023 10:30:51 -0700 In-Reply-To: References: <43864caecd65d02081d623d05ccc1683@anastigmatix.net> <94a0e631b787d56fec1b17e03fe045b5e14907c1.camel@j-davis.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.44.4-0ubuntu2 MIME-Version: 1.0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Thu, 2023-10-05 at 07:31 -0400, Robert Haas wrote: > It's a lot of infrastructure for the project to carry > around for a feature that's probably only going to continue to become > less relevant. Agreed, at least until we understand the set of users per-column encoding is important to. I acknowledge that the presence of per-column encoding in the standard is some kind of signal there, but not enough by itself to justify something so invasive. > I suppose you never know, though. On balance I think it's better to keep the code clean enough that we can adapt to whatever unanticipated things happen in the future; rather than to make the code very complicated trying to anticipate everything, and then being completely unable to adapt it when something unanticipated happens anyway. Regards, Jeff Davis