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 1kGcwQ-00087s-IM for pgsql-pkg-yum@arkaria.postgresql.org; Fri, 11 Sep 2020 06:53:51 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kGcwO-000687-Mr for pgsql-pkg-yum@arkaria.postgresql.org; Fri, 11 Sep 2020 06:53: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 1kGU7J-0003Sh-2C for pgsql-pkg-yum@lists.postgresql.org; Thu, 10 Sep 2020 21:28:31 +0000 Received: from mail-cy1usg02on0093.outbound.protection.office365.us ([23.103.209.93] helo=USG02-CY1-obe.outbound.protection.office365.us) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1kGU7F-0003dc-85 for pgsql-pkg-yum@lists.postgresql.org; Thu, 10 Sep 2020 21:28:27 +0000 ARC-Seal: i=1; a=rsa-sha256; s=arcselector5401; d=microsoft.com; cv=none; b=utNSl9nL18bSjOHCAcPfDXGTsQ1lpVc94KBLW6F6keX3uUUAmexOTpCCfwXM1uDvYvazsZU03pEWBRhmo1BhnHw4VoyWUuuk+9Va5SXxchLZEztmglQUNRp+sCOONTzk/2gvrvDRAtrvx46vrGFzbUphQZqC0V2UNWNwSTNdsf7N30Kxsx+dDRGoI23Wetic3/driqc6JYSfcRHX4wCPp9zXoXlPW5P2FiyeuY+QEbLgwY3IdWWVno4RZtREP1Pqh/1oLHRww/d0QcZgu6BWxgiwEOSYbiX+Uk8V24/LtlY3iwwCBaliTk34ielWQezBDAaZp8uDD/HucM0AislvNw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector5401; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=s0tVAv4nHOgJ1YSDAZ7fzC6Iok9FbGZx2838Ti18R6Q=; b=FOhYI4wlUR68emjtNXagErRp0En5FtclioPZNxt46pEsrGQC015Chzhi3JYlJ9EhVicMM93qBkGCy2Ti91vBXwmhNA5Gz854bJrtjhBd3pf3QMDYN4aI0f0ErmOD0E6Ni/HL2pT0DWcKe9hzdXA/NriP5aChVN1dMhUmEQGeqj+7A0PKa1f4u5qqQBZNsN/mMVEuhXa3WcDKDhaxUBB1xloEdLinkvwQM0UfEPoYfQlJEmkTt1B1vpkFdayZf2gePsyMLH3apLsk4mhbzomwRPRIquCs8kXiDUUdXecEwYxWu5uWUJsApcjV4ZGKONSm8A6q5S0HAUdX6j6hO8n8ww== ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=gdit.com; dmarc=pass action=none header.from=gdit.com; dkim=pass header.d=gdit.com; arc=none DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gdit.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=s0tVAv4nHOgJ1YSDAZ7fzC6Iok9FbGZx2838Ti18R6Q=; b=DvqNiNojSzSwY6PGwxjCrIHHLa9xl3/DuMiFJHVlAhvha7mb8HljfIh/VHwHUUyC4aRHl/hijuo2SarvARkJd8K2shOMbopDxKvmDrYDPj3ugCyk0gpP+CMR6fzEYRcwxJMvVQiDonR2/3PUnrUTvGnr9MaaWO3A/gRwaL37kjw= Received: from DM3P110MB0505.NAMP110.PROD.OUTLOOK.COM (2001:489a:200:413::17) by DM3P110MB0361.NAMP110.PROD.OUTLOOK.COM (2001:489a:200:411::15) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3370.16; Thu, 10 Sep 2020 21:28:19 +0000 Received: from DM3P110MB0505.NAMP110.PROD.OUTLOOK.COM ([fe80::180d:16fd:1b46:65d4]) by DM3P110MB0505.NAMP110.PROD.OUTLOOK.COM ([fe80::180d:16fd:1b46:65d4%2]) with mapi id 15.20.3370.016; Thu, 10 Sep 2020 21:28:19 +0000 From: "Josserand, Jesse F (NE)" To: "pgsql-pkg-yum@lists.postgresql.org" Subject: Need some assistance please Thread-Topic: Need some assistance please Thread-Index: AdaHqxe8K1152+kJT5mpo5bqAR163w== Date: Thu, 10 Sep 2020 21:28:19 +0000 Message-ID: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-dg-ref: PG1ldGE+PGF0IG5tPSJib2R5Lmh0bWwiIHA9ImM6XHVzZXJzXGplc3NlLmpvc3NlcmFuZFxhcHBkYXRhXHJvYW1pbmdcMDlkODQ5YjYtMzJkMy00YTQwLTg1ZWUtNmI4NGJhMjllMzViXG1zZ3NcbXNnLThhMDc0Y2VjLWYzYWMtMTFlYS05YzNiLWE0NGNjODNiYTY1MlxhbWUtdGVzdFw4YTA3NGNlZC1mM2FjLTExZWEtOWMzYi1hNDRjYzgzYmE2NTJib2R5Lmh0bWwiIHN6PSI5NDUwIiB0PSIxMzI0NDI0Njg5NzQ1Mzg3MzkiIGg9IjA3ZjIwdDZTSGJaRnZoVHowbFRNSzhNTmxLND0iIGlkPSIiIGJsPSIwIiBibz0iMSIvPjwvbWV0YT4= authentication-results: lists.postgresql.org; dkim=none (message not signed) header.d=none;lists.postgresql.org; dmarc=none action=none header.from=GDIT.com; x-originating-ip: [155.95.90.253] x-ms-publictraffictype: Email x-ms-office365-filtering-correlation-id: a641c152-8923-45ba-3405-08d855d06fff x-ms-traffictypediagnostic: DM3P110MB0361: x-microsoft-antispam-prvs: x-ms-oob-tlc-oobclassifiers: OLM:10000; x-ms-exchange-senderadcheck: 1 x-microsoft-antispam: BCL:0; x-forefront-antispam-report: CIP:255.255.255.255;CTRY:;LANG:en;SCL:1;SRV:;IPV:NLI;SFV:NSPM;H:DM3P110MB0505.NAMP110.PROD.OUTLOOK.COM;PTR:;CAT:NONE;SFS:(4636009)(366004)(5660300002)(966005)(26005)(71200400001)(8676002)(6506007)(498600001)(186003)(55016002)(2906002)(52536014)(8936002)(9686003)(86362001)(6916009)(166002)(66446008)(7696005)(66476007)(64756008)(66556008)(66946007)(76116006)(33656002)(3480700007)(83380400001);DIR:OUT;SFP:1102; x-ms-exchange-transport-forked: True Content-Type: multipart/alternative; boundary="_000_DM3P110MB050560DDBC804087CA4EE7E296270DM3P110MB0505NAMP_" MIME-Version: 1.0 X-OriginatorOrg: gdit.com X-MS-Exchange-CrossTenant-AuthAs: Internal X-MS-Exchange-CrossTenant-AuthSource: DM3P110MB0505.NAMP110.PROD.OUTLOOK.COM X-MS-Exchange-CrossTenant-Network-Message-Id: a641c152-8923-45ba-3405-08d855d06fff X-MS-Exchange-CrossTenant-originalarrivaltime: 10 Sep 2020 21:28:19.1690 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 43243701-7aa8-421a-a131-fed3f11104c8 X-MS-Exchange-CrossTenant-mailboxtype: HOSTED X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM3P110MB0361 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --_000_DM3P110MB050560DDBC804087CA4EE7E296270DM3P110MB0505NAMP_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Hello support team. I'm doing some work for GDIT on gov't project and in my analysis of environ= ments have found some issues most of which I can resolve myself, but there = are 3 things I could use your direction on, if you please... 1. May I get specific instructions on how to do the appropriate yum r= epo update for postgresql as described at a high level on this page: https:= //yum.postgresql.org/news/new-repo-rpms-released/. I'm running on both Cent= OS 7.8 and RHEL 7.8 in my 2 main environments. 2. I want to convert to 'dnf' from 'yum' and could use a 1, 2, 3-styl= e write-up of that procedure. 3. Finally, and this is most important of all... my instances of Post= greSQL were at 10.10 when I got here. I have taken them from there through = 10.11, 10.12, 10.13, and now 10.14 successfully. However, I just discovered= that the DBA/Sysadmin before me did not correctly migrate nor update PostG= IS when going from some version of 9.x.x to 10.10 before I took over. I hav= e discovered the existence of PostGIS 2.5 in 2 databases out of all the dat= abases in my instance of PostgreSQL 10.14. What do I need to do, if anythin= g, to ensure they are up-to-date and useable? Please provide a detailed ste= p-by-step. Thanks in advance! :) Jess [TekSynap - Technology Moving at the Speed of Thought] Jesse F. Josserand | Sr. Systems Architect/SysAdmin/DB Analyst M: 601-590-0304 | D: 228-469-2019 | jesse.josserand@teksynap.com www.TekSynap.com | 1760 Reston Parkway, Suite = 515, Reston VA 20190 Assigned to GDIT Project, 294 Thames Avenue, Bay St. Louis, MS 39520 Jesse.Josserand@GDIT.com [Connect with TekSynap on LinkedIn] | [Save vCard] --_000_DM3P110MB050560DDBC804087CA4EE7E296270DM3P110MB0505NAMP_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Hello support team.

I’m doing some work for GDIT on gov’t pr= oject and in my analysis of environments have found some issues most of whi= ch I can resolve myself, but there are 3 things I could use your direction = on, if you please…

1.     &= nbsp; May I get specific instructions on how to do the ap= propriate yum repo update for postgresql as described at a high level on th= is page: https:/= /yum.postgresql.org/news/new-repo-rpms-released/. I’m running on = both CentOS 7.8 and RHEL 7.8 in my 2 main environments.

2.     &= nbsp; I want to convert to ‘dnf’ from ‘= yum’ and could use a 1, 2, 3-style write-up of that procedure.

3.     &= nbsp; Finally, and this is most important of all… m= y instances of PostgreSQL were at 10.10 when I got here. I have taken them = from there through 10.11, 10.12, 10.13, and now 10.14 successfully. However= , I just discovered that the DBA/Sysadmin before me did not correctly migrate nor update PostGIS when going from som= e version of 9.x.x to 10.10 before I took over. I have discovered the exist= ence of PostGIS 2.5 in 2 databases out of all the databases in my instance = of PostgreSQL 10.14. What do I need to do, if anything, to ensure they are up-to-date and useable? Please prov= ide a detailed step-by-step.

Thanks in advance!

J
Jess

3D"TekSynap

Je= sse F. Josserand&n= bsp; |  Sr. Systems Architect/SysAdmin/DB Analyst
M: 601-590-0304  |  D: 22= 8-469-2019  = |  jesse.josserand@teksynap.com
w= ww.TekSynap.com  |  1760 Reston Parkway, Suite 515, Reston VA 20190
Assigned to GDIT Pr= oject, 294 Thames Avenue, Bay St. Louis, MS 39520
Jesse.Josserand@GDIT.com

3D"C=

 = | 

3D"Save<= /span>

 

 

--_000_DM3P110MB050560DDBC804087CA4EE7E296270DM3P110MB0505NAMP_--