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.96) (envelope-from ) id 1vx3dr-00CzS8-0o for pgsql-admin@arkaria.postgresql.org; Mon, 02 Mar 2026 13:48:59 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vx3cq-0010VZ-2K for pgsql-admin@arkaria.postgresql.org; Mon, 02 Mar 2026 13:47:57 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vx3cq-0010VQ-1J for pgsql-admin@lists.postgresql.org; Mon, 02 Mar 2026 13:47:56 +0000 Received: from [89.231.102.37] (helo=mail.localities.work) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.98.2) (envelope-from ) id 1vx3co-000000001ce-3GkY for pgsql-admin@lists.postgresql.org; Mon, 02 Mar 2026 13:47:55 +0000 Received: from localhost (localhost [127.0.0.1]) by swir.mine.priv (Postfix) with ESMTP id A6575C01408B for ; Mon, 02 Mar 2026 14:47:50 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=localities.work; h=in-reply-to:from:from:content-language:references:subject :subject:user-agent:mime-version:date:date:message-id :content-type:content-type:received:received; s=dkim20251117; t= 1772459269; x=1773323270; bh=lDFWFj/LyP1Z7ZNYgtrSDJOindn7wsdRSN6 o7Oheai4=; b=b+X1KmUfQ2KQnpOes5wr7doVdh6bDIufIG2rAmy+/Gv9vKgJihJ 6h1VbKNxocuT9tx8N01dWBfKPs4IbFNu/Icd14YnVstEdSyx8AE20/CYuqrh11yq 69l5NOQjT6wApSoDXdcAv0KMJ668stAyXMISjFOJgOnd36/LXljjQgUY= X-Virus-Scanned: amavis at mine.priv Received: from swir.mine.priv ([127.0.0.1]) by localhost (swir.mine.priv [127.0.0.1]) (amavis, port 10022) with LMTP id 2sUNDh3ClHBE for ; Mon, 2 Mar 2026 14:47:49 +0100 (CET) Received: from [10.3.0.10] (unknown [10.3.0.10]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange x25519 server-signature ECDSA (prime256v1) server-digest SHA256) (No client certificate requested) by swir.mine.priv (Postfix) with ESMTPSA id DCD51C014085 for ; Mon, 02 Mar 2026 14:47:49 +0100 (CET) Content-Type: multipart/alternative; boundary="------------PjW36wR0Ls3QIq3u0bzFCOin" Message-ID: <0bdbf1e5-e8ab-408d-8e0e-f4e3df6a3c1d@localities.work> Date: Mon, 2 Mar 2026 14:47:50 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: upgrade from 13 to 16 To: Pgsql-admin References: <7e69fa35-05c7-4cd9-9eba-90fd78b7cd18@localities.work> Content-Language: en-MW, pl, pl-PL From: listy In-Reply-To: X-Host-Lookup-Failed: Reverse DNS lookup failed for 89.231.102.37 (failed) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------PjW36wR0Ls3QIq3u0bzFCOin Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit So, for now & the future "issues"... Since on LInux - unless tampered with manually - binaries get replaced upon upgrades of a package: Is it worthwhile tampering with binaries as opposed to starting anew and with a backup? (which I eventually did, I get it might be a personal preference) many thanks, L. --------------PjW36wR0Ls3QIq3u0bzFCOin Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit So, for now & the future "issues"...
Since on LInux - unless tampered with manually - binaries get replaced upon upgrades of a package:
Is it worthwhile tampering with binaries as opposed to starting anew and with a backup? (which I eventually did, I get it might be a personal preference)

many thanks, L.
--------------PjW36wR0Ls3QIq3u0bzFCOin--