Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1id887-0003qZ-Rc for pgsql-bugs@arkaria.postgresql.org; Fri, 06 Dec 2019 07:34:24 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1id886-0004Gb-Ig for pgsql-bugs@arkaria.postgresql.org; Fri, 06 Dec 2019 07:34:22 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1id886-0004GT-61 for pgsql-bugs@lists.postgresql.org; Fri, 06 Dec 2019 07:34:22 +0000 Received: from mail-pg1-x52a.google.com ([2607:f8b0:4864:20::52a]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1id882-0006oR-Nn for pgsql-bugs@lists.postgresql.org; Fri, 06 Dec 2019 07:34:21 +0000 Received: by mail-pg1-x52a.google.com with SMTP id b9so2470114pgk.12 for ; Thu, 05 Dec 2019 23:34:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ridenext-co-in.20150623.gappssmtp.com; s=20150623; h=from:to:cc:references:in-reply-to:subject:date:message-id :mime-version:content-transfer-encoding:thread-index :content-language; bh=YEMfhUlFT3h3uncF17/fB2qVXXDWlA1wogu+QSsGMP4=; b=Vvr5l4zGSl44MQCnyANbopQcHU/UZ15uqWwirEC0TH9WKulfDywe4kRqS0hvf+n1XG Z246b3MoSVmP/NwLNUsYPhIVzjaxZ5RV8cQJingxBkAdLh9E2mU6NS/Es8iuL2kfHIcK yTfcGPiFlASauQ/9+e25SChnFFCNKL7QjpYQmLcw+I/ZfYGWs4oQbubjGAu5uNEC0G1A yObIqNO8nMKio/wJJ3mmoTlDcZtnB0lZnoZuz61xhkw6X9vLM4mhFrfKkapPEQn0uxj1 1OfAxPdVhGkXb8UmxtwNZb/jcQZIybGDOcZv+FsNxEIurD5gpatVA1buJiHpWf0oTfWe 5WwA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:references:in-reply-to:subject:date :message-id:mime-version:content-transfer-encoding:thread-index :content-language; bh=YEMfhUlFT3h3uncF17/fB2qVXXDWlA1wogu+QSsGMP4=; b=GyvQF7cswRc3r82RzX8Xi9wzYuuXK4gIueaC9eUgY0WbdMTPJF0H1ooGovpZFx14/e kgykLY30YkxSVHRIp1JUWzLY3zGpHGGBUNrdpdsrl1GhSFyDZEuoizTf0sjWnD3EwPe8 nKWsm1+XBz5xHFXGDFc1CX+fJw163rEWplAMdSmo7PvS/zb4nbA698j0a88qKyv+NbPe CzX23dU+XdTQkxuXlUP0pTYt1Vr3NZoNkoW2eNl0k/5AZyOajyyKm4KPnbVtdo7UOxSP ffrh/Z/yLGiLUdpps81IT20rQPlyOv2ApezQ+bRBKnpuTucYvpyDxORGrveOSJcJcVkc 1aeg== X-Gm-Message-State: APjAAAUgdBNPnnTtbTIYyQpYdD6pz8mqbhEzSfev/aPQwcQaTA5UU6tI Qgmn7o+C6mvLJy68Ji3xXh7zig== X-Google-Smtp-Source: APXvYqy1Mhu+GKFJdYAx6IHqzM27GMJDvimJj+lfD0LdVW2/z/4xrr09S88Knja1oMCnusw8CYPS4A== X-Received: by 2002:a65:5ccc:: with SMTP id b12mr1988950pgt.124.1575617656616; Thu, 05 Dec 2019 23:34:16 -0800 (PST) Received: from LAPTOPSTDSG1KI ([180.151.43.98]) by smtp.gmail.com with ESMTPSA id 186sm15124658pfe.141.2019.12.05.23.34.15 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 05 Dec 2019 23:34:16 -0800 (PST) From: "RideNext" To: "'Greg Clough'" Cc: References: <00ad01d5a5b8$83731320$8a593960$@ridenext.co.in> <001201d5ab59$dfd3b3d0$9f7b1b70$@ridenext.co.in> In-Reply-To: Subject: RE: Postgres takes more than 6 minutes to come up during host/standby switch over Date: Fri, 6 Dec 2019 13:04:13 +0530 Message-ID: <007401d5ac07$908dd360$b1a97a20$@ridenext.co.in> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Outlook 16.0 Thread-Index: AQGZn12KBEv1DJNRRjJfXuprznY24wJhlxgYAirdMhgB/WYgG6fwdFGA Content-Language: en-in List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Hi Greg, Thank you for the quick response and suggestions. Thanks! -----Original Message----- From: Greg Clough Sent: 05 December 2019 19:27 To: RideNext Cc: pgsql-bugs@lists.postgresql.org Subject: RE: Postgres takes more than 6 minutes to come up during host/standby switch over > So we would like to know if we upgrade to latest version will it be > smooth upgrade? Do you suspect any issues during upgrade and factors > to be considered? For example any of API name or format would change > in the latest version? Major upgrades require testing and if you're jumping from 9.2 to 12, then you're skipping ahead 7 major releases... so it will be a large undertaking to validate your application, but you should start ASAP so you can move to an environment that's secure. If PostgreSQL is that old then I suspect your OS is also quite old, and won't have fixes for major things like Heartbleed, etc. https://www.postgresql.org/docs/current/upgrading.html If you're unsure on how to build new servers and then migrate the data, then this is something I would suggest you need to hire a consultant to help with. In either case, this isn't a PostgreSQL bug so let's close this thread, and if you want to post into a different forum then choose something like pgsql-admin or pgsql-general: https://www.postgresql.org/list/ Regards, Greg. ________________________________ This e-mail, including accompanying communications and attachments, is strictly confidential and only for the intended recipient. Any retention, use or disclosure not expressly authorised by IHSMarkit is prohibited. This email is subject to all waivers and other terms at the following link: https://ihsmarkit.com/Legal/EmailDisclaimer.html Please visit www.ihsmarkit.com/about/contact-us.html for contact information on our offices worldwide.