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 1tYfbL-00Cwon-KX for pgsql-general@arkaria.postgresql.org; Fri, 17 Jan 2025 06:13:04 +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 1tYfbK-0097P5-2t for pgsql-general@arkaria.postgresql.org; Fri, 17 Jan 2025 06:13:02 +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 1tYSyu-00Fysk-Te for pgsql-general@lists.postgresql.org; Thu, 16 Jan 2025 16:44:33 +0000 Received: from mail-qt1-x82c.google.com ([2607:f8b0:4864:20::82c]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1tYSyt-000nfd-17 for pgsql-general@postgresql.org; Thu, 16 Jan 2025 16:44:33 +0000 Received: by mail-qt1-x82c.google.com with SMTP id d75a77b69052e-467a6781bc8so10030761cf.2 for ; Thu, 16 Jan 2025 08:44:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1737045869; x=1737650669; darn=postgresql.org; h=cc:to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=+wsN3R4ZKd+mp72C+fLk5dn/k2BtkAZzSWwxxoOr75Q=; b=YhiGapt0xWyjaCVZ0PPgEYSpM+piLIWIwur5AVbmJ4xCXkYGe8CIc/gE/N5DLExrNv obZGzNJl/H8CMslrLfHi9hR7wzsM7Ayn1v5nh3xQ7EsScPMS/hiCBK+ucep4fWZ+N0PH d0CCVcYk+r6WdakHl1Z7ybBeLA8ysITR082+R+FuppXVqGkKMuB0lxNAGMpm24NOsQxm EyohVDnT3wpS+gLpt1iVOtd8bT3bZaiWkGN/F6qCkFTw7bNdkmTkV7dwW36nRBn7eC09 hgDaj9ZnjoEXkNRpruqbm83tbiu0g6jL0D/Uiw0Bi/7XSIOwld/p8dO2XqGo4TaynL29 Av9A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1737045869; x=1737650669; h=cc:to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=+wsN3R4ZKd+mp72C+fLk5dn/k2BtkAZzSWwxxoOr75Q=; b=cT5mG/NTGuJUbR0Rc0pF3KbdztPGhpheAV9CpDe2whqP/0WKGZ0YNQV8uOW6oUQkLZ 7/XYBdiBmIAm2F4fiia3W/RpNDNHlEeZYbeDEEWXDdAGVNyVn7QMfThUVTyAUwjKP6y0 WrxWxZuENVJHZ3qLI5pua/Og3GITMzZHdOCrAJbvSS1e+1agQjCqD347XDk3HcYr5Ryg 1dE2SrCrXFkUA34Bg0+kEW+EnRcMpYRMkgfRAjfCWhlypgf2IScerd06fZxU6ShIto6j Oe8pFcvDi2j8hwCGL0sDCgSetEIJkP0XMuc8QlXwCD2ltyctRPIBWwr+Krlb/CNLnxtq 5DfQ== X-Gm-Message-State: AOJu0YzubXIxKT/ZJEm8uvso06gOm7uoSWEQpj30mFvqj1O7h1C/jfuZ G9ILhwACdWRlfkm5HDIcGq7Mmqni/GoplxcmROO4Ed0ECyKgsGb5BfXvN0L9kzSOq3sPNDIBb0d aw6qc77fMOsUUoxZSty/ur8hxMs/7dHnrgTwn X-Gm-Gg: ASbGncuhblinQrRKZuLF9/aEOfYfCMPaYwi3PnL7/B9SZW6Bih2LZX1CUJpL+hZFO1b HDCMAgXk8PCJHQO01Wjt8gCNRbE4VNC2heSRX8w== X-Google-Smtp-Source: AGHT+IFpCgaF/LIGpIdLcRhO1LVb7dFcA5FkZ6mocNh69yhnAm1vCSOthoO36YxZ834weB85NxjNHyNosMIWxEkmA28= X-Received: by 2002:a05:622a:49:b0:467:84a7:5147 with SMTP id d75a77b69052e-46c7107a92dmr523592991cf.39.1737045869598; Thu, 16 Jan 2025 08:44:29 -0800 (PST) MIME-Version: 1.0 From: Kamen Kalchev Date: Thu, 16 Jan 2025 18:44:18 +0200 X-Gm-Features: AbW1kvbkj54jSPZeQzLCYeq-WSXDlTgoLNbutxfgEm-ph9c0SQJgaiVFicUIJqs Message-ID: Subject: glibc 2.35-2.39 upgrade requirements To: pgsql-general@postgresql.org Cc: abubakarm94@gmail.com Content-Type: multipart/alternative; boundary="000000000000041bcf062bd58284" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000041bcf062bd58284 Content-Type: text/plain; charset="UTF-8" Hi everyone, we're planning to upgrade the OS running Postgres from ubuntu jammy to ubuntu noble. As part of the OS change, the glibc version will be changed from glibc 2.35 to glibc 2.39.. Can someone confirm if changing the glibc between those versions will require a full reindex of the Postgres cluster? Thanks in advance. --000000000000041bcf062bd58284 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi everyone, we'= re planning to upgrade the OS running Postgres from ubuntu jammy to ubuntu = noble. As part of the OS change, the glibc version will be changed from gli= bc 2.35 to glibc 2.39..=C2=A0

Can someone confirm if changing the glibc between those versio= ns will require a full reindex of the Postgres cluster?=C2=A0

Thanks in advance.
--000000000000041bcf062bd58284--