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.92) (envelope-from ) id 1j94sY-0007Vf-M5 for pgsql-hackers@arkaria.postgresql.org; Tue, 03 Mar 2020 10:34:23 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1j94sW-00008J-9m for pgsql-hackers@arkaria.postgresql.org; Tue, 03 Mar 2020 10:34:20 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1j94sV-000089-QI for pgsql-hackers@lists.postgresql.org; Tue, 03 Mar 2020 10:34:20 +0000 Received: from mail-pj1-x1043.google.com ([2607:f8b0:4864:20::1043]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1j94sS-0007Aj-Ai for pgsql-hackers@postgresql.org; Tue, 03 Mar 2020 10:34:18 +0000 Received: by mail-pj1-x1043.google.com with SMTP id s8so1152531pjq.0 for ; Tue, 03 Mar 2020 02:34:16 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enterprisedb-com.20150623.gappssmtp.com; s=20150623; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=rBWSk5cobneSjTl+NOuKyrDNDQcqrWD3FOmgnzM1zXA=; b=0cuZhLQoYumchLRXRV58KoXb73lkyJ0FIDlZGAYOm0bOxkOKhtOGoT1gNCq19pYr6o Et+8v3SEm5AVRCfmv9t7/BuCN1/ALVx2c/a5cdi1x0SUjJz1+EocoX54TRx8A5Vshz8i pfoHJT6t+lD7qz/RJiOMFd03FK7r4vfeT01MqgEmLordhKv/nLyQFbEADKB3iDWFH9Y2 TmB9MNmSlJ+oLe1jxSzHCrzI2yI4mybqrxeZ6oviBgyperxkIDf5c3FIjiindW38qfmR C/rC+z/+BT0Uf6ODTJgn97IA5HY6OeBwjiFEC4PthiaGZevngY1ir4c2kv9eqlxGQptN 91xQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=rBWSk5cobneSjTl+NOuKyrDNDQcqrWD3FOmgnzM1zXA=; b=n8KuOsYY2S3kPDglQm76ZZMEK3R0GaJKBbMGux2kmo4P950UVQvMrPedXyNw5b3pAx e8T1EKW5XBprCdP/3gBdQhl2QaXyiKSkQxk1B09GbOJc7lxGBNpCjws4XNzIL7Gjr2ZN hPpCQRZKHjgFhD/Zs27AjP/WG3tLahCAg89bxFR1Y9bjFriXi+q72lp1xgha11YmPGZb rMeddF3bQ2CpnaPeVh5t8aIkOQ0CbGNPZNX+ueJrqPrXp0MVe9TINFcQY/f9qN8xnFRa FVaeQh6FZSc0C2HE7c4HER+aE5x7FTK7mUil0y5d91hfO1XAJ/qHRQ5QakebfkeyU4qe LcgA== X-Gm-Message-State: ANhLgQ2QTVcQV51qH3f0qaQVkdcA7yYZ8PmVN1DmRuIYJa2rxwj2vI1z 6qsm1FzSr9YQ5nnlFwRkL51XuV3GOmzTyoDGW75aNChLKSMULjl/56you+nwpqSjB+sJateuT0V SI3a8WRQQephLVVLTRsPs2D2jplc9674jDrwYXQXjy/XTvWg1ajyTaJMzrxB/LZgddXd1SQ7Sxc b0Z4Ci77iGm6cyDwT4XgxSaJi3xqW/Tg== X-Google-Smtp-Source: ADFU+vvtmUrbLhbuQcnC5Vevu2LsFRnEyn5aSOVqRMBbVMR5smAtERhdeENNC5YB3kUK6t0HFA418A== X-Received: by 2002:a17:90b:14c2:: with SMTP id jz2mr3248672pjb.152.1583231654867; Tue, 03 Mar 2020 02:34:14 -0800 (PST) Received: from localhost.localdomain ([114.143.109.178]) by smtp.gmail.com with ESMTPSA id y193sm8603034pfg.162.2020.03.03.02.34.11 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 03 Mar 2020 02:34:14 -0800 (PST) Subject: Re: backup manifests To: Robert Haas , Suraj Kharage Cc: Rushabh Lathia , Tels , David Steele , Andrew Dunstan , PostgreSQL Hackers , Jeevan Chalke , vignesh C References: From: tushar Message-ID: Date: Tue, 3 Mar 2020 16:04:07 +0530 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US X-CLOUD-SEC-AV-Info: edb,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 On 2/27/20 9:22 PM, Robert Haas wrote: > Here's a new patch set for this feature. Thanks Robert.  After applying all the 5 patches (v8-00*) against PG v13 (commit id -afb5465e0cfce7637066eaaaeecab30b0f23fbe3) , There are few issues/observations 1)Getting segmentation fault error if  we try pg_validatebackup against  a valid backup_manifest file but data directory path is WRONG [centos@tushar-ldap-docker bin]$ ./pg_basebackup -D bk --manifest-checksums=sha224 [centos@tushar-ldap-docker bin]$ cp bk/backup_manifest /tmp/. [centos@tushar-ldap-docker bin]$ ./pg_validatebackup -m /tmp/backup_manifest    random_directory/ pg_validatebackup: * manifest_checksum = f0460cd6aa13cf0c5e35426a41af940a9231e6425cd65115a19778b7abfdaef9 pg_validatebackup: error: could not open directory "random_directory": No such file or directory Segmentation fault 2) when used '-R' option at the time of create base backup [centos@tushar-ldap-docker bin]$ ./pg_basebackup -D bar -R [centos@tushar-ldap-docker bin]$ ./pg_validatebackup  bar pg_validatebackup: * manifest_checksum = a195d3a3a82a41200c9ac92c12d764d23c810e7e91b31c44a7d04f67ce012edc pg_validatebackup: error: "standby.signal" is present on disk but not in the manifest pg_validatebackup: error: "postgresql.auto.conf" has size 286 on disk but size 88 in the manifest [centos@tushar-ldap-docker bin]$ -- regards,tushar EnterpriseDB https://www.enterprisedb.com/ The Enterprise PostgreSQL Company