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 1srLOj-000lAf-DR for pgsql-general@arkaria.postgresql.org; Thu, 19 Sep 2024 17:56:58 +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 1srLOg-005Sw9-NO for pgsql-general@arkaria.postgresql.org; Thu, 19 Sep 2024 17:56:56 +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 1srLOg-005Sw0-CL for pgsql-general@lists.postgresql.org; Thu, 19 Sep 2024 17:56:55 +0000 Received: from mail-lj1-x233.google.com ([2a00:1450:4864:20::233]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1srLOe-0003Tl-4H for pgsql-general@lists.postgresql.org; Thu, 19 Sep 2024 17:56:55 +0000 Received: by mail-lj1-x233.google.com with SMTP id 38308e7fff4ca-2f759b87f83so12503471fa.2 for ; Thu, 19 Sep 2024 10:56:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1726768612; x=1727373412; darn=lists.postgresql.org; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=uuHWgAFT7pDgJylacfQUfBeXk94It2hGRy5OQm1bZco=; b=g3SZaTPqEWdJE2QxUDbARoOL31mjgEj34v6e6vBRf88sc0eSd3FJtkH3bUUVBSUuYy 8kZXbOeq/CjGtTeHsWCRvj5qGtEmo5uQyxuOiLQzbvAGyPSFG5vPKJv/U5TZkuc3Tkhn /bBwdE/V0uHwpSFc2EDcNe7br4/wonP/aPvKfVfbVIyin8HicKm1SAwnMpqGWX/qrVUO irFnkbwgv+3ET0eWIi5aYYeX/mT6M0KB3GmPpWb9H4MTWO4gYvP0sv4VwSCAznElKtW9 QAXrufr5iLMw4SE/05/yMbRuI4UynvZoqT3pocul36yZhyrFQhRqUqx0myYJWIldamYG xGGA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1726768612; x=1727373412; h=to:references:message-id:content-transfer-encoding:cc:date :in-reply-to:from:subject:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=uuHWgAFT7pDgJylacfQUfBeXk94It2hGRy5OQm1bZco=; b=MyoqXcaZkpxNZOooWDythfofQyXIfOZfn9j+n0kSYHyp6THRFh+UIEyvKX7DqlFh1F 0OfTomSJu3A1QnVidjgf93VK94asXBmB0eDcvmbpohQ9VMoXvRTADuXwa84zLFTrQuTp fhnbGhe3j4bV1HdGI0UdI6f5G0BYXzOZ1Nn9pOTJPxC7HtJqA2gHf7W3t/QwRNebhBH+ 328hg534ukvq07DEY9pknn8WPASYVqkmn2jBq/TA5b1ZDvPzYgIGxQXHP6WqSWw6tJyo c0T/LOSdhfbi5V5UaC290EXgJXXA921teXIlFEsrb+fI5pCrK4IUr3cVdterEy1jAeZn ykig== X-Gm-Message-State: AOJu0YyaAFsS7lDNjpnkOMf1Y0tpZ+mIayUcU5qKPtmxaPck1+smv7PU 0fZUE9qj144R9rNfFprEuC/sUk7CsohVQcvU62/rbR/F5XXDt4MmrFvIsw== X-Google-Smtp-Source: AGHT+IFpEqCFRGDaEQPczCb1fE67xldqBDeY934f9IO1ejp5Cywa8D1H+TExeZhz2u9J+ZecigHbxQ== X-Received: by 2002:a05:651c:168f:b0:2ef:1784:a20 with SMTP id 38308e7fff4ca-2f7cb34848amr2410371fa.38.1726768612206; Thu, 19 Sep 2024 10:56:52 -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 4fb4d7f45d1cf-5c42bb55a13sm6330953a12.30.2024.09.19.10.56.50 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 19 Sep 2024 10:56:51 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3818.100.11.1.3\)) Subject: Re: glibc updarte 2.31 to 2.38 From: Paul Foerster In-Reply-To: <1991352.1726758874@sss.pgh.pa.us> Date: Thu, 19 Sep 2024 19:56:20 +0200 Cc: pgsql-general list Content-Transfer-Encoding: quoted-printable Message-Id: References: <1991352.1726758874@sss.pgh.pa.us> To: Tom Lane 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 Tom, > On 19 Sep 2024, at 17:14, Tom Lane wrote: >=20 > No, I wouldn't expect that to be necessary. I was hoping one of the pros would say that. =F0=9F=A4=A3 > Maybe. We don't really track glibc changes, so I can't say for sure, > but it might be advisable to reindex indexes on string columns. Advisable is a word I undfortunately can't do much with. We have = terabytes and terabytes of data in hundreds of databases each having = potentially hundreds of columns that are candidates. Just reindexing and = taking down applications during that time is not an option in a 24x7 = high availability environment. Cheer, Paul