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 1nyf0f-0004SS-9S for pgsql-hackers@arkaria.postgresql.org; Tue, 07 Jun 2022 19:37:01 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nyf0e-0004YJ-5k for pgsql-hackers@arkaria.postgresql.org; Tue, 07 Jun 2022 19:37:00 +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 1nyf0d-0004Y6-S3 for pgsql-hackers@lists.postgresql.org; Tue, 07 Jun 2022 19:36:59 +0000 Received: from mail-lj1-x22a.google.com ([2a00:1450:4864:20::22a]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1nyf0b-0005Fs-Cl for pgsql-hackers@postgresql.org; Tue, 07 Jun 2022 19:36:59 +0000 Received: by mail-lj1-x22a.google.com with SMTP id y29so20362346ljd.7 for ; Tue, 07 Jun 2022 12:36:57 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=vAmki2TTUp4xm0wp+GlsSZ4ptSLxEVreU8KdUokrlbk=; b=EO+1zMbPvr5WdQh6Rz+z3wvgMqb7YOa4gaiXvOQXy/nm6Qh9dRBkVVwGxZvi9anL9h pvc8iz10c7FYRoHE3lD5slCa45rSuv5SHu4GBLqzUJAl4ZtZL1HERsdkKHBKAm4CYlYZ MUlaiPPAxzYWBqYWjdWQjvHEEXXhXzwkVbwpKPJ6e4iK//ygfHoN/JVsVK64sgvPp0kK KWw9qY8shxtJoV8fes48n/LKpXIzU+XVq97v9AkE+VhNb/pPW/2YeN0YzuSZj5Tuab+p AlnrhRjHiKEsqvxf0ALGnGO4CMcfBWH/QPlKDmdPIDnF6DwHnZjcqIy6C1DRYbKlxiQX aHSg== 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=vAmki2TTUp4xm0wp+GlsSZ4ptSLxEVreU8KdUokrlbk=; b=cL4C6h/eIrBvDkWzecH3fAQ4CmmrrfwExTAhWN4kJ2Y5OjVU0uqGeeJCqRGHVonTjM vjOz+YIKXK0E45Nl8D/sJIWIrg7gW4VX2aAG9wzJM7cMkz2yZYtMYg2SByurSTkS9opi PefwL/+urrtCSYYG9O/8oFZDCVjZbwNKe9ByGwMgji28lYrV8E8Rh6yVPEEYfS5MgpDT BsbnY5RA49McilZDa8Qvrn8+la09F9QSaTfn/vdA8lfWq7xDMkpTxSVKDqA+Bja/TRT6 tzAHuga6Af8om7lCYJDQu5tCc41UiwU1iNwLrC8RoEyPL6Z/6DmNcJUkGtTo26vUaoiN hPtw== X-Gm-Message-State: AOAM532aJTs0lFUd+lDdrV0jcghFBhBEg7IbxPaJnsDXWsUsRDyJQUAX h2WUoDYxtEZ0V+YB5oaKvWKDdxOva0wjQQbzL/0= X-Google-Smtp-Source: ABdhPJz96v/qdGwtPmvNJlYEZeCiuGBw6PlPHj+Q+SPX76KFDWo5qqrCQyjRtr+aDA8ThJa8eyLZc2hNtEWJCf2d0bo= X-Received: by 2002:a2e:80d3:0:b0:255:5c62:7614 with SMTP id r19-20020a2e80d3000000b002555c627614mr22313291ljg.389.1654630615767; Tue, 07 Jun 2022 12:36:55 -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> In-Reply-To: <366234.1654289888@sss.pgh.pa.us> From: Robert Haas Date: Tue, 7 Jun 2022 15:36:45 -0400 Message-ID: Subject: Re: Collation version tracking for macOS To: Tom Lane Cc: Thomas Munro , 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 3, 2022 at 4:58 PM Tom Lane wrote: > I think the real problem here is that the underlying software mostly > doesn't take this issue seriously. Unfortunately, that leads one to > the conclusion that we need to maintain our own collation code and > data (e.g., our own fork of ICU), and that isn't happening. Unlike > say Oracle, we do not have the manpower; nor do we want to bloat our > code base that much. You don't, but that opinion isn't universally held, or at least not with the same vigor that you hold it. See e.g. https://www.postgresql.org/message-id/a4019c5e570d4dbb5e3f816c080fb57c76ab604a.camel%40cybertec.at and subsequent discussion, for example. In fact, I'd go so far as to argue that you're basically sticking your head in the sand here. You wrote: "Given the lack of complaints, it doesn't seem like this is urgent enough to mandate a post-beta change that would have lots of downside (namely, false-positive warnings for every other macOS update)." But you wrote that to Peter, who was essentially complaining that we hadn't done anything, and linked to another source, which was also complaining about the problem, and then Jeremy Schneider replied to your email and complained some more. Complaining about "false positives" doesn't really make sense to me. It's true that we don't have any false positives right now, but we also have no true positives. Even a stopped clock is right twice a day, but not in a useful way. People want to be notified when a problem might exist, even if sometimes it doesn't actually. The alternative is having no idea at all that things might be broken, which is not better. -- Robert Haas EDB: http://www.enterprisedb.com