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 1jqXJz-0007zR-SG for pgsql-admin@arkaria.postgresql.org; Wed, 01 Jul 2020 07:38:19 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jqXJy-0002ph-Ov for pgsql-admin@arkaria.postgresql.org; Wed, 01 Jul 2020 07:38:18 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jqXJy-0002pa-Ci for pgsql-admin@lists.postgresql.org; Wed, 01 Jul 2020 07:38:18 +0000 Received: from mail-ej1-x642.google.com ([2a00:1450:4864:20::642]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1jqXJs-0002kG-8f for pgsql-admin@postgresql.org; Wed, 01 Jul 2020 07:38:17 +0000 Received: by mail-ej1-x642.google.com with SMTP id w6so23464306ejq.6 for ; Wed, 01 Jul 2020 00:38:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec-at.20150623.gappssmtp.com; s=20150623; h=message-id:subject:from:to:date:in-reply-to:references:user-agent :mime-version:content-transfer-encoding; bh=jnJoGKhRD65zOlkwXZxUJtbXIYvrAaV24rxOZRQmy0s=; b=uBUTV91poXCop11C1YTQ740OT++21aPqmwC3jJPJOSCGKarIpYOL9o50pR32kr0k07 bmKQ1WyAv/NAbgteiv0u8kT8bNs1WsXRMwpMNC4vlfICcCg/pnR8q5uIiGf0r+qI5p1X hPhC+86v5L4G/yp1RYTp1v/z/Ot9G/nEbZFdAVbmviPUrrjSsImEIj4SDKnFEXO5mYca FZ2kNkhtExey7LxJcxIZJ9TPH+LimbNcjf7viPL6XOcmtj5SkJR+ql6+/jpq5CfW0Cq5 BP0Oawoc/DLxnw+zoCAhrE1jV2A8mVbFYp7RB7uRXIW6Tzx3lvUAAWBLxd/5enGw/6G0 btEA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:date:in-reply-to :references:user-agent:mime-version:content-transfer-encoding; bh=jnJoGKhRD65zOlkwXZxUJtbXIYvrAaV24rxOZRQmy0s=; b=jgQrux9/6NBuzZTvb08lJo0Av+2aYh24kKgOQJWaOgPgQsD2NtCWyRzZa+ZcON5ZnZ scSX/r3sV8BgR+HMe2y/Z/3CKWEtCC5EocoFm2lTrKNQEJEtLN9sr1ubRwQQdy8czKDr c+CcdOM0Wpyqs0Ud/6TgNWe0JLE4LMHRgQTIBSiJbcfWFAkjUaM0djQU2QOq/+TURmdj wwtP+bpfrIEXP2xNuTwl7Rmvj1isCLKp1rUj8HjT5pIR41aoeLjLKvcfMDUSc1tWuIdC CTDfBT92Ko+Uys1r2H1ppu3HsLlqDHMyeA5N4oeCZeWqggit1IqY+sWRz74QbXcp2L43 lObA== X-Gm-Message-State: AOAM532EVwkZDvhgKCr73u15xfzgwWHg+B4W6ndQ4Etsg3RGHXIhQ7XN coadenCvQ5tIgVqMB1+83724Ng== X-Google-Smtp-Source: ABdhPJyoUem5xUaCbZ+CA/GlXMnC02mUOCHQXbu0Jnk0YYS1YRHbkvwqZgcN3BNXx55sw17ueNvYAw== X-Received: by 2002:a17:906:fa9a:: with SMTP id lt26mr12351607ejb.502.1593589090486; Wed, 01 Jul 2020 00:38:10 -0700 (PDT) Received: from localhost.localdomain (217-149-170-133.nat.highway.telekom.at. [217.149.170.133]) by smtp.gmail.com with ESMTPSA id x9sm4032969ejw.28.2020.07.01.00.38.09 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 01 Jul 2020 00:38:09 -0700 (PDT) Message-ID: <9f08d0b2aeb76d9775acf18b6bb70fac0ae51d2b.camel@cybertec.at> Subject: Re: [HELP] Query regarding failover From: Laurenz Albe To: Praveen Kumar K S , pgsql-admin@postgresql.org Date: Wed, 01 Jul 2020 09:38:08 +0200 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.32.5 (3.32.5-1.fc30) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Tue, 2020-06-30 at 20:54 +0530, Praveen Kumar K S wrote: > My requirement is to set up a process to handle failover and recovery without manual intervention. > I would like to know your suggestions if there is any standard way of doing this or is it better to write custom scripts. I don't think you can do that reliably with "custom scripts". There is no standard way, but have a look at Patroni. Yours, Laurenz Albe -- Cybertec | https://www.cybertec-postgresql.com