Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1gEpgP-0002Lt-KU for pgsql-admin@arkaria.postgresql.org; Tue, 23 Oct 2018 05:56:49 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gEpgM-0006Kv-V3 for pgsql-admin@arkaria.postgresql.org; Tue, 23 Oct 2018 05:56:46 +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_SHA384:256) (Exim 4.89) (envelope-from ) id 1gEpgM-0006Ko-Mm for pgsql-admin@lists.postgresql.org; Tue, 23 Oct 2018 05:56:46 +0000 Received: from st11p00im-asmtp002.me.com ([17.172.80.96]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gEpgF-00077e-D1 for pgsql-admin@postgresql.org; Tue, 23 Oct 2018 05:56:45 +0000 Received: from process-dkim-sign-daemon.st11p00im-asmtp002.me.com by st11p00im-asmtp002.me.com (Oracle Communications Messaging Server 8.0.2.2.20180531 64bit (built May 31 2018)) id <0PH100J00EQ69100@st11p00im-asmtp002.me.com> for pgsql-admin@postgresql.org; Tue, 23 Oct 2018 05:56:14 +0000 (GMT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mac.com; s=04042017; t=1540274174; bh=mYWyH8cCD5dPQTKizRD5oQKmf0DX8UrMB1nMJYjno/g=; h=From:Content-type:MIME-version:Subject:Date:To:Message-id; b=jtBqqjjvrg4e6Ryq/tNKwpV3rDAIScYFRVhZhv1OSCCiECYpISXzsxnTBH3aX83Jd g3i3nLZPu5nt20FDm8wQ3eoyVw1M68wwFnCJQ3s4lNzDieG3uB1NQc/kp6hriO3CRD wlzRcggf4vw6UwzaKacM0P5Bi1gpcU0Cy1om5PSn+k+E2uGRhxnyXqcCbhoe6u1qi2 QiWRjkMeLpof3RM+/cddQ6p8Ef0LbcdrVQeRNo4rm2QomLIj7Z+092vdCr6w73MRu8 AwymUMLyzpTZyA4LGK8ACL6zAmncdATlAf2zvxQ4M8SiMrGsGGWPOqHekSUCCn27hb g7qc/hfKYL/OA== Received: from icloud.com ([127.0.0.1]) by st11p00im-asmtp002.me.com (Oracle Communications Messaging Server 8.0.2.2.20180531 64bit (built May 31 2018)) with ESMTPSA id <0PH100IAGF5K6P20@st11p00im-asmtp002.me.com>; Tue, 23 Oct 2018 05:56:13 +0000 (GMT) X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 mlxscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1807170000 definitions=main-1810230053 X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2018-10-23_02:,, signatures=0 From: Evan Bauer Content-type: text/plain; charset=utf-8 Content-transfer-encoding: quoted-printable MIME-version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Subject: Re: Point in time Recovery in Postgres? Date: Tue, 23 Oct 2018 01:56:06 -0400 References: <1540269835111-0.post@n3.nabble.com> To: pavan95 , pgsql-admin@postgresql.org In-reply-to: <1540269835111-0.post@n3.nabble.com> Message-id: X-Mailer: Apple Mail (2.3445.9.1) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Since pg_dump is logical, it won=E2=80=99t provide the basis for PITR. = A number of other tools will. There is a good discussion of the capabilities of most of the PostgreSQL = backup tools here: = https://severalnines.com/blog/top-backup-tools-postgresql=20 Cheers, - Evan Evan Bauer eb@evanbauer.com +1 646 641 2973 Skype: evanbauer > On Oct 23, 2018, at 00:43, pavan95 = wrote: >=20 > Hi all, >=20 > Is it possible to do PITR in postgres for a database provided that = database > pg_dump backup is available and archive logs are also configured.... >=20 > Could you please confirm? Thanks in Advance!! >=20 >=20 > Regards, > Pavan >=20 >=20 >=20 > -- > Sent from: = http://www.postgresql-archive.org/PostgreSQL-admin-f2076596.html >=20