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 1n2DMM-00058a-0Q for pgsql-admin@arkaria.postgresql.org; Tue, 28 Dec 2021 14:21:50 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1n2DMK-0004Hi-4T for pgsql-admin@arkaria.postgresql.org; Tue, 28 Dec 2021 14:21:48 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1n2DMJ-0004HW-JK for pgsql-admin@lists.postgresql.org; Tue, 28 Dec 2021 14:21:47 +0000 Received: from mail-pg1-x533.google.com ([2607:f8b0:4864:20::533]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1n2DMF-000725-Dm for pgsql-admin@lists.postgresql.org; Tue, 28 Dec 2021 14:21:46 +0000 Received: by mail-pg1-x533.google.com with SMTP id m15so16111990pgu.11 for ; Tue, 28 Dec 2021 06:21:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=ZHtHuG1dWLGtLToLVKMvIkJCosN580FHXQjhQ5TmODo=; b=PMH6NeXBvmUUA+sb5x6anmcediFv3wku2bxvXub67zU+/7zYp+csAi40jLjvlMo6U1 8IyBiZ8Q5nOLjehO7tnqisfZ/KKt6nY1iFUxPq4JcWsN0tTthsoKm8WnwjkiQ0IE5bEc SHgNF9xYB0dZZXicAsn5BvtFa5uFVqMQzw4RWJ3GY8Vqz/ZkKI7ojzcAjJ29eLGLKGWF hEqmWouwO7xXDYdR/epFOxR8fY6DntmPA1s+tmdQioQgwopGXLJLcBrNAf9ojA3COUi1 OGtMznzMurH7RU0Z9hP6H0rqS+iU2D3ad86Am8T1zfYinNkG3BSKRRV5nvgu6fwICfIT XGag== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=ZHtHuG1dWLGtLToLVKMvIkJCosN580FHXQjhQ5TmODo=; b=np85+Q0SuMbcjP09SGWXtWVDt2SL67HYGFJBcWzk2EHcZA8Jx/aBW+UkJfHrsC0EX+ Yv/x4pP5FzO1kFo9gEumPxEldynL2nxBwy00gqRgHawU+G1CMIhBubvh4YcRncy8+2Uq nUKbQwQbpDN4dTZ2xgCO79Im9brgvqUsOzyjUMXlFqNFDvq1KAMSLVUSwMdKYN7lAJBR y6mJa8LplveUu8QgWybQnHFlYVWIWYkP6wxUg/cSQ7bI/pmf9g/t+PA2nr6MRjgoqsSV UsDx7roVUQO7mrXIsc6LFRxihwIW8nxBE+v1bFhDQj3AbrpForsJxuGcMRzRCQXdy8sh Nduw== X-Gm-Message-State: AOAM532C+MTuj2Esxn5jCmcBzvfLo+Isa1e7rxh8OGODg6r7xxF6sP9+ YnDkC+XgZwATYOKsnAJ2qgM= X-Google-Smtp-Source: ABdhPJwVXLul5SSrKOCzeGSg2bZCEpcJwf/zY1pmZkAz2cAoH6UiLKm4yHvIASjAufW2Xcpd65W2+w== X-Received: by 2002:a63:b245:: with SMTP id t5mr4137622pgo.388.1640701302183; Tue, 28 Dec 2021 06:21:42 -0800 (PST) Received: from [192.168.1.3] ([122.171.158.207]) by smtp.gmail.com with ESMTPSA id v63sm17649019pgv.71.2021.12.28.06.21.40 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 28 Dec 2021 06:21:41 -0800 (PST) From: Ravi GH Message-Id: <5678103F-59DC-437F-89B5-96C7DF91C8CF@gmail.com> Content-Type: multipart/alternative; boundary="Apple-Mail=_F14023A7-81BF-43B0-BD88-D4A1F87795B4" Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.7\)) Subject: Re: Pg upgrade from 10.x to 12.x recommendations Date: Tue, 28 Dec 2021 19:51:37 +0530 In-Reply-To: Cc: Tom Lane , Pgsql-admin To: kaido vaikla References: <42AA8DD8-B4C7-4850-90DC-D7BE77BE1ED9@gmail.com> <1513791.1640626827@sss.pgh.pa.us> X-Mailer: Apple Mail (2.3608.120.23.2.7) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --Apple-Mail=_F14023A7-81BF-43B0-BD88-D4A1F87795B4 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Thanks a lot for the URLs shared, I could easily compare my = postgresql.conf file changes and identified features like = restart_after_crash are very helpful and also CVE fixes. The provided links helped very much. > On 28-Dec-2021, at 1:06 PM, kaido vaikla = wrote: >=20 > Hi,=20 > A few helpful url's > https://why-upgrade.depesz.com/show?from=3D10&to=3D12.9 = > https://pgconfig.rustprooflabs.com/param/change/10/12 = > and if You don't use an exp-imp for pg upgrade then for indexes > = https://blog.crunchydata.com/blog/just-upgrade-how-postgresql-12-can-impro= ve-your-performance = > br > Kaido >=20 > On Mon, 27 Dec 2021 at 19:40, Tom Lane > wrote: > Ravi GH > writes: > > What are the recommended / major features/security fixes added to PG = 12.x which makes upgrade to PG 12.x is critical now. >=20 > Reading the release notes would help you decide. >=20 > https://www.postgresql.org/docs/release/ = >=20 > regards, tom lane >=20 >=20 --Apple-Mail=_F14023A7-81BF-43B0-BD88-D4A1F87795B4 Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=us-ascii
Thanks a lot for = the URLs shared, I could easily compare my postgresql.conf file changes = and identified features like restart_after_crash are very helpful and = also CVE fixes.
The provided links helped very = much.



On = 28-Dec-2021, at 1:06 PM, kaido vaikla <kaido.vaikla@gmail.com> wrote:

Hi, 
A few = helpful url's
https://why-upgrade.depesz.com/show?from=3D10&to=3D12.9=
https://pgconfig.rustprooflabs.com/param/change/10/12
and if You don't use an exp-imp for pg upgrade then for = indexes
https://blog.crunchydata.com/blog/just-upgrade-how-postgresql-1= 2-can-improve-your-performance
br
Kaido

On Mon, 27 Dec 2021 at 19:40, Tom Lane = <tgl@sss.pgh.pa.us> wrote:
Ravi GH <mails2ravi@gmail.com> writes:
> What are the recommended / major features/security fixes added to = PG 12.x which makes  upgrade to PG 12.x is critical now.

Reading the release notes would help you decide.

https://www.postgresql.org/docs/release/

                    =     regards, tom lane



= --Apple-Mail=_F14023A7-81BF-43B0-BD88-D4A1F87795B4--