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 1nzsQy-0006f6-88 for pgsql-hackers@arkaria.postgresql.org; Sat, 11 Jun 2022 04:09:12 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nzsQx-0007Pc-61 for pgsql-hackers@arkaria.postgresql.org; Sat, 11 Jun 2022 04:09:11 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nzsQw-0007PS-T0 for pgsql-hackers@lists.postgresql.org; Sat, 11 Jun 2022 04:09:10 +0000 Received: from mail-ed1-x535.google.com ([2a00:1450:4864:20::535]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1nzsQu-0004K5-H0 for pgsql-hackers@postgresql.org; Sat, 11 Jun 2022 04:09:10 +0000 Received: by mail-ed1-x535.google.com with SMTP id 25so1126265edw.8 for ; Fri, 10 Jun 2022 21:09:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bowt-ie.20210112.gappssmtp.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=7BHlOy/DXJyTq6vJADKNzMavKyb3actTjKJEf1S/Oo0=; b=qPdeoz3KCNPq5RsXBOrEwDJe2i7X1LIBEYwQByN1s74mDxoAl1ogACYTTxpnxyR9WH /hectMgRvOTFkAlWO7FpnD9z4/uecIl63baTqnlptgnkafv9HQNRpBFwqswAbtsupW7q L5jwZolHyjJn/m3qq4TGbfmSsSLcBea6cmiNVK/FNNSrV9IRTIqdCkrXutzwI39bC8oP UsuHxS+2Zi2poTNllzbXdTQBatuJNdVBpw4VMfkE4iJ8yYqkut6d1kM5fJ5dQ592jkok OeMFzF0LXWiwXP2mYJhGvGw1f9l9ZLTq+YxZrFAIPaXHADx2AnXpjsA50wdfDjpxXHYP zsdg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=7BHlOy/DXJyTq6vJADKNzMavKyb3actTjKJEf1S/Oo0=; b=TqVGZ7TMmt+UNxS1v2/EvC8Izj8x3Zjqbklhs6YKqw5aFwA9f4XYwZ+XLbnln63d0W EX7xyYbK+COXov88aJslH1bGbZ31WT3voOKp2y2VKU4Vuz3QT5gJYPZYL+62hexhkfXT 1xyd8FG6uSGLSkQRFK5Z4JqMUVPYRD3nPxOhtuZZ/3Gn3wL8djLmS0dsnOb9i/NQAoBJ RAYJPU7EsFpo0Dh7cfCWuoElqxIepbSWrZ9/GpL1rmLI1u88ccMt0LIy8LAFBRoI7yy0 nV6Ovu5cPzW2pfYCtH5WBU+/RylpfeY97UYk37Ndx71g4hgDPEE9oZdjzGKDE/oPq8HQ kUpA== X-Gm-Message-State: AOAM532v/9VyB2JqPdU11XJT3TPL0MkmnUJEmilL6oCIRr2fjpvfpS86 ks1u8SMrOvRnFjpsze3Gl8n4062jHjH34wzCo6bHCw== X-Google-Smtp-Source: ABdhPJymv8wy/k2rElo8v+6dgsfWEM8CBrdF2zAbz4ynVIm7YZISA6TQjCUzm8k61jahk1glIDXZSKhDFyvZ6CVdfcY= X-Received: by 2002:a05:6402:c8b:b0:42f:ac38:9c07 with SMTP id cm11-20020a0564020c8b00b0042fac389c07mr45687370edb.292.1654920547354; Fri, 10 Jun 2022 21:09:07 -0700 (PDT) MIME-Version: 1.0 References: <381977b1-0898-cb6f-a427-3b5d873e81bd@enterprisedb.com> <231072.1654273317@sss.pgh.pa.us> <1874de62-6bec-4bc1-1d14-0a2730b125da@ardentperf.com> <366234.1654289888@sss.pgh.pa.us> <0867fe37-abbd-77ba-aafc-572074978bb0@amazon.com> In-Reply-To: From: Peter Geoghegan Date: Fri, 10 Jun 2022 21:08:41 -0700 Message-ID: Subject: Re: Collation version tracking for macOS To: Thomas Munro Cc: "Finnerty, Jim" , "Nasby, Jim" , Tom Lane , Jeremy Schneider , Peter Eisentraut , pgsql-hackers Content-Type: text/plain; charset="UTF-8" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Fri, Jun 10, 2022 at 8:47 PM Thomas Munro wrote: > I'm also suspicious that there are more subtle hazards like pathkeys > lurking in the shadows. We go to great effort to recognise matching > and non-matching collations by OID alone, which is why my first > attempt was "distinct [OIDs]", so that'd keep working. It's definitely possible that we won't be able to find a workable solution that deals with "time travel collations" sensibly from the planner's perspective. It's certainly not a neat adjunct to what we have. I think that it *might* be possible to find a way to make it work that is suboptimal, but works. Without being overly clever. The DB2 docs say "use the CLDR version prefix to avoid unexpected changes in behavior when upgrading to future releases of the Db2 database". But if you don't do that, and get a change in behavior, then surely any related indexes must have been rebuilt too. The interesting part may be what that upgrade looks like in detail. -- Peter Geoghegan