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 1kpQW9-0001Hg-Nz for pgadmin-hackers@arkaria.postgresql.org; Wed, 16 Dec 2020 06:42:33 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kpQW8-0001Fb-NF for pgadmin-hackers@arkaria.postgresql.org; Wed, 16 Dec 2020 06:42:32 +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 1kpQW8-0001FU-I7 for pgadmin-hackers@lists.postgresql.org; Wed, 16 Dec 2020 06:42:32 +0000 Received: from mail-io1-xd31.google.com ([2607:f8b0:4864:20::d31]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1kpQW6-0008OF-0J for pgadmin-hackers@postgresql.org; Wed, 16 Dec 2020 06:42:31 +0000 Received: by mail-io1-xd31.google.com with SMTP id p187so22951197iod.4 for ; Tue, 15 Dec 2020 22:42:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enterprisedb-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=4G/4CpP8227HXi09w1TwrmqsGpnlt58+GmkeTR/4hCU=; b=Il1sMrDn229ih6kVcj0QWU365hhfCR85Xu73YlBMJjdzr4hq9cEYzMuZHlfbEgQWmI bIx8pHXk0RWN3/hmxb72Q3YOcjpqa8xpBiUnz9RRqz3Q6jV4GstNbGaqQbtosiujUU2h PR7g36/ODAjCx2YVWZ+uCcmvkxHkpTIm2KQ7Nbv+hig5E8WqXbQ12j1rmljXBPX/9xxK GHw81JOi2XELShYc95/XKW6taCWzGeMaN+POV4mhwhg0FlzP30brNyF2GVrWch6J6DBh RXCsLPcJLjyqXjZ/vJ6czZA/Aa7KMXdbCtOfpZz2f1c2d1xu59dTfEyFijo0uqI46Rxp qSrw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=4G/4CpP8227HXi09w1TwrmqsGpnlt58+GmkeTR/4hCU=; b=JR2vuDVmysOPpCQH9XqQ1LFqfHF6n1s6v8IieSWbFUjisQgogjV/PCI/hBre1fhvza O735VYZXVSixUEHZgIJCrd0w+jdW9cZ1tuATDkol8uirfxC5GCfDxE5xeXOLNNs5ED9f Jy78MulXTXomibng44H1mRPBkAmO81F7AR32it+7mvshTTD71TALFI4TECAq4eVKbvrz Vt0/5cAexSC8CeV6AJX2SNMHSqHJv4o8Qowc56KR8k86ssUbT6Q6kdkSeHlH5drxx8xa kkkVSqQ5AjP+UHyaGmt5vlZUopW5jKtw5UGBJQFuJKSYjxktqJZI1mPRz3973cP/Vq2V u6Jg== X-Gm-Message-State: AOAM531OXrKHdUfzaUrWbBI/Na7fdaqFou4VTSHC7zSDcCOznPWHS6/S Flnp8SdqtqcYft4YVWkXG5cocGjrGlZvfScOIlJuUV/F0P0CFt/UYCsb6FpC+d8sgdmGBVTEkmd 7jkq0CHQH2Z5b1ZVfJPnWA9mVAul19gT2uKFDUoz/qWncNbzFDgXmUNJBUxuaf2JFYmEM8KEe6W vJN+VL7Yl9Ve5FEcqzxbl6ibnxLhX0SCK2WKWTLr0yWBDxKSfV4rUUBaKY3A== X-Google-Smtp-Source: ABdhPJys6JERsyUlBKZ53XLGtp+jE9IwRDq80UrbQttlyF4DnUfQ4jaixsPEHH/IRtppf+KHvgIAWgwG5ZKPaEyYSME= X-Received: by 2002:a02:c90f:: with SMTP id t15mr41656092jao.20.1608100948877; Tue, 15 Dec 2020 22:42:28 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: From: Akshay Joshi Date: Wed, 16 Dec 2020 12:12:18 +0530 Message-ID: Subject: Re: [pgAdmin] RM5875 template1 is shown after you use pg_upgrade To: Rahul Shirsat Cc: pgadmin-hackers Content-Type: multipart/alternative; boundary="000000000000d23e6d05b68f2d82" X-CLOUD-SEC-AV-Info: enterprisedb,google_mail,monitor X-CLOUD-SEC-AV-Sent: true X-Gm-Spam: 0 X-Gm-Phishy: 0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --000000000000d23e6d05b68f2d82 Content-Type: text/plain; charset="UTF-8" Thanks, patch applied. On Tue, Dec 15, 2020 at 2:46 PM Rahul Shirsat < rahul.shirsat@enterprisedb.com> wrote: > Hi Hackers, > > Please find the attached patch below which resolves the issue of showing > template1 after pg_upgrade. > > Testing of the patch has been done on : > > 1. Windows Server 2016 (PostgreSQL 12.5, compiled by Visual C++ build > 1914, 64-bit & PostgreSQL 13.1, compiled by Visual C++ build 1914, 64-bit) > 2. MacOSX > > > -- > *Rahul Shirsat* > Senior Software Engineer | EnterpriseDB Corporation. > -- *Thanks & Regards* *Akshay Joshi* *pgAdmin Hacker | Principal Software Architect* *EDB Postgres * *Mobile: +91 976-788-8246* --000000000000d23e6d05b68f2d82 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Thanks, patch applied.

On Tue, Dec 15, 2020 at 2:46 PM = Rahul Shirsat <rahul.s= hirsat@enterprisedb.com> wrote:
Hi Hackers,

Plea= se find the attached patch below which resolves the issue of showing templa= te1 after pg_upgrade.

Testing of the patch has bee= n done on :
  1. Windows Server 2016 (PostgreSQL 12.5, compile= d by Visual C++ build 1914, 64-bit & PostgreSQL 13.1, compiled by Visua= l C++ build 1914, 64-bit)
  2. MacOSX

--
Rahul Shirsat
Senior S= oftware Engineer=C2=A0|=C2=A0EnterpriseDB=C2=A0Corporation.


--
Thanks & Regards
Akshay Joshi
pgAdmi= n Hacker | Principal Software Architect
EDB Postgres
Mobile: +91 976-788-8246

--000000000000d23e6d05b68f2d82--