Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nzAfD-0006TC-R1 for pgsql-hackers@arkaria.postgresql.org; Thu, 09 Jun 2022 05:24:59 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nzAfC-0007Jc-Fe for pgsql-hackers@arkaria.postgresql.org; Thu, 09 Jun 2022 05:24:58 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nzAfC-0007JK-2e for pgsql-hackers@lists.postgresql.org; Thu, 09 Jun 2022 05:24:58 +0000 Received: from mail-pl1-x62c.google.com ([2607:f8b0:4864:20::62c]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1nzAf9-00046h-A7 for pgsql-hackers@postgresql.org; Thu, 09 Jun 2022 05:24:56 +0000 Received: by mail-pl1-x62c.google.com with SMTP id u18so19426710plb.3 for ; Wed, 08 Jun 2022 22:24:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ardentperf-com.20210112.gappssmtp.com; s=20210112; h=content-transfer-encoding:from:mime-version:subject:date:message-id :references:cc:in-reply-to:to; bh=scPSSSt38dbD/D63K5oxgCZ5G4WqdRZ7jFiVwP7vT10=; b=vZjspBLIaBPe48qOjTi6f8Lhcr2S5oAL9ROmbwrF0dsAq7/oLDtcaXaEB4ShWIbmWh CJEiYc4pc5X6y8qrJmwF5FTIoB8b3B15eWlR+0PL01jKATQpV+9pNRtjj9gWsImh8z1r bwhI+GcJFCsKUUw+mfi+BFOMZ/Ngh75np7AXXLJGGunD9dv2Y2DcOAREWLar+p4BNTaf 9jYbqucVqSR2cqi5zi2Qkfe9lLgDpTttLy7RmLCmRLdsYZyeXEzIA0xdoC+/HMKx2Elc mIrsKtpIvhBsNfK2sJ5ITMEFtaBzYyQgMv74IF54n3lCNAOJVdi0mqPG1bXqTuly7BR9 WsAQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:content-transfer-encoding:from:mime-version :subject:date:message-id:references:cc:in-reply-to:to; bh=scPSSSt38dbD/D63K5oxgCZ5G4WqdRZ7jFiVwP7vT10=; b=FhFh7zJ0q/x9h7KhS5GLnTpSzjSkx9F1x8s2hWlMTgVpjJqycc5KeLSLTNcZXC+nKF vtg9Ld6ff1O2lCbkX6gd6Q4hI831NzCpdROBntpmI0BpZdx0xYjaqzJa8f5Gn9R207rZ GENI4wJlMkdLqO2SZCvG7OhuG7AafZBxrixqIX1ncwJ83Ps7K2mr8KJeG0SABXhdwLf6 9FtgnrGjixYzPdNOU8a2khlmdcz1Wxnf51pPrsc7LOyTIpZ6Y/GgmgbH3BJbEmR+twqJ 0nxQFOW3vEw9y1DbfO0I4qAnB8QfkpDqE7bC6dFCXOUmr805L2nThgzcH+Sw458u5ci3 8jUg== X-Gm-Message-State: AOAM532geKDU3bwhOeMoGNgNwBGYqBUF+ghvp/9qybrcyDgijGIZ2ENS 3PCCWyZHxGYbrpmJ/SP8AGbvdA== X-Google-Smtp-Source: ABdhPJwZaCHGwvR+oz+wuDB1cFwuDVghBT1o9cgXsF6k+R95tssEMiGevtxldagaUdEubwgmItiyrQ== X-Received: by 2002:a17:90b:1d08:b0:1e4:dad9:64e5 with SMTP id on8-20020a17090b1d0800b001e4dad964e5mr1654930pjb.200.1654752294222; Wed, 08 Jun 2022 22:24:54 -0700 (PDT) Received: from smtpclient.apple (c-24-17-46-25.hsd1.wa.comcast.net. [24.17.46.25]) by smtp.gmail.com with ESMTPSA id 129-20020a621787000000b005180c127200sm15978989pfx.24.2022.06.08.22.24.53 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 08 Jun 2022 22:24:53 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable From: Jeremy Schneider Mime-Version: 1.0 (1.0) Subject: Re: Collation version tracking for macOS Date: Wed, 8 Jun 2022 22:24:49 -0700 Message-Id: <171D0968-0F8D-4522-B348-19D683364D9E@ardentperf.com> References: Cc: Peter Geoghegan , Jim Nasby , Tom Lane , Peter Eisentraut , pgsql-hackers In-Reply-To: To: Thomas Munro X-Mailer: iPhone Mail (19F77) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk > On Jun 8, 2022, at 03:19, Thomas Munro wrote: >=20 > =EF=BB=BFOn Wed, Jun 8, 2022 at 12:23 PM Peter Geoghegan wrot= e: >> ISTM that there are two mostly-distinct questions here: >>=20 >> 1. How do we link to multiple versions of ICU at the same time, in a >> way that is going to work smoothly on mainstream platforms? >>=20 > Yeah. Well I couldn't resist doing some (very!) experimental hacking. > See attached.=20 Even if PG supports two versions of ICU, how does someone actually go about r= emoving every dependency on the old version and replacing it with the new? C= an it be done without downtime? Can it be done without modifying a running a= pplication? Avoiding =E2=80=9Ccollate=E2=80=9D clauses on SQL statements req= uires working behind the scenes with defaults and indexes and partitions and= constraints and everything else. I=E2=80=99m having a hard time coming up w= ith a way this would be possible in practice, with all the places collations= can show up. Is the idea of =E2=80=9Calter database=E2=80=9D to change the default collat= ion even realistic? I=E2=80=99m having a bit of trouble picturing what the end game is here -Jeremy Sent from my TI-83