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 1srIIT-000Qn0-I8 for pgsql-general@arkaria.postgresql.org; Thu, 19 Sep 2024 14:38:18 +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 1srIIR-002C6R-At for pgsql-general@arkaria.postgresql.org; Thu, 19 Sep 2024 14:38:16 +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 1srIIQ-002C6J-W2 for pgsql-general@lists.postgresql.org; Thu, 19 Sep 2024 14:38:16 +0000 Received: from mail-ej1-x635.google.com ([2a00:1450:4864:20::635]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1srIIO-00023T-JM for pgsql-general@lists.postgresql.org; Thu, 19 Sep 2024 14:38:15 +0000 Received: by mail-ej1-x635.google.com with SMTP id a640c23a62f3a-a7a843bef98so112658566b.2 for ; Thu, 19 Sep 2024 07:38:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1726756693; x=1727361493; darn=lists.postgresql.org; h=to:date:message-id:subject:mime-version:content-transfer-encoding :from:from:to:cc:subject:date:message-id:reply-to; bh=/mwZFfLB2h9qMHjWoxoaRu18quMxSoz9UXta4zE7kNE=; b=X854YqTRKUhG6ZJUkrCIXps8KsKprGqi8MGzVL/rD6VagN+4tRsyG1qlFb/4BEFL5H 8RuGcCyUTxMDge64k7XuHt827691k1jHMwRAsTtoIG2T9M8keqRNQJSXWZXQ5RelxODO NtD8f5GCKHQE1sse4tYuzQgTjponLlqgcV//N/jezvk80L6AZAfIWvJBr/xmSgCimGh8 yEZ/U77mxxJLlTWXHJzgJ4WCj/a1bKpkxTLbvqbwY5N9fInTJjsMUn9CcONwjX6HFdpN ksZFBb4J5x/eHzN/SvmVV7H1fm2y7A48DOoVSqUJ9aGkV9gIjvp5ol5nrk737zG8aspy yvKA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1726756693; x=1727361493; h=to:date:message-id:subject:mime-version:content-transfer-encoding :from:x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=/mwZFfLB2h9qMHjWoxoaRu18quMxSoz9UXta4zE7kNE=; b=Cb+gx6qsA8ez1kDkkGzE95nZCO9rYJiUOdG7KcNgWx6Bbv0fpS35aTc/CRneE3mGK3 1V9wceAm3PeOXAWg4IFdBKX/4l/CrFw/oGDOwHd3SgKPDaIY4gLfovBSN4qc9W+Bjulp 8n7b62A/jJZqpt/z8v6IRm6Q7VP/ghU1VJOego1+Z5D189gx+ihgbdHIbe0jOsIzsbFM EhQt0Nqv0+6E+P29FcKRItsBSN63OtRB1EPXjSmNEwpKEyYG3inBVfEKuYei7ulQacQy nMNAhy0WJyt4ioZG3pYCpqv/XpUqGDXc9sZ6gArk/vgO8ceV3DeDAxwe3vKwBTYy6bIl ogMA== X-Gm-Message-State: AOJu0YytFMS/fFxGLr98R1PpkuaXRaP07dgpC/yfkdePBTdOGzzXccyd 1bXNVJO9UdHayxsvfOg+N8iqBOnSq9lHhPvumu5NUbEmamta8HHiAD90UQ== X-Google-Smtp-Source: AGHT+IEB0oFCmS0tn4+PNcnOTKw4NHiWkik4VEFhpS0phSfWqCxdqR/3AWtJM6EiCxrjACIP3V0+jw== X-Received: by 2002:a17:907:72d2:b0:a8a:6db5:7e42 with SMTP id a640c23a62f3a-a9047b45665mr2238280466b.9.1726756693222; Thu, 19 Sep 2024 07:38:13 -0700 (PDT) Received: from smtpclient.apple (26-36-239-77.dyn.cable.qlnet.ch. [77.239.36.26]) by smtp.gmail.com with ESMTPSA id a640c23a62f3a-a90612b3067sm733503866b.98.2024.09.19.07.38.12 for (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 19 Sep 2024 07:38:12 -0700 (PDT) From: Paul Foerster Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3818.100.11.1.3\)) Subject: glibc updarte 2.31 to 2.38 Message-Id: Date: Thu, 19 Sep 2024 16:37:41 +0200 To: pgsql-general list X-Mailer: Apple Mail (2.3818.100.11.1.3) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hi, we have SLES 15.5 which has glibc 2.31. Our admin told us that he's = about to install the SLES 15.6 update which contains glibc 2.38. I have built our PostgreSQL software from source on SLES 15.5, because = we have some special requirements which the packages cannot fulfill. So = I have questions: 1) Do I have to build it again on 15.6? 2) Does the glibc update have any impact? I recall having to have = everything reindexed when the 2.28 update came due to major locale = changes, but I didn't have to do it since then. 3) Where and how can I find out if it is necessary to reindex? And how = can I find out what indexes would be affected. I'd really appreciate your comments. Thanks very much in advance. Paul=