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 1j1FgN-0004tw-EL for pgsql-novice@arkaria.postgresql.org; Mon, 10 Feb 2020 20:29:27 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1j1FfN-00070x-NS for pgsql-novice@arkaria.postgresql.org; Mon, 10 Feb 2020 20:28:25 +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 1j1FfN-00070p-7B for pgsql-novice@lists.postgresql.org; Mon, 10 Feb 2020 20:28:25 +0000 Received: from mail-wr1-x441.google.com ([2a00:1450:4864:20::441]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1j1FfF-0005kx-Pl for pgsql-novice@lists.postgresql.org; Mon, 10 Feb 2020 20:28:23 +0000 Received: by mail-wr1-x441.google.com with SMTP id g3so8360249wrs.12 for ; Mon, 10 Feb 2020 12:28:17 -0800 (PST) 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=Wq8SgS+S++92WjdxAtu+TjrAUKELKI7lQyCPDnPOKtk=; b=rrJLcBpTD2bE5UKIQwRyuarBNqDa374G2SHCOIUJvyZi06cXqhKFoDwp9hiaf/Z7mw 6ZgJbcfBg773XKTbyy/DyBuLKSsxi5Lgc6bUKdzwZdV3zUNm+WKoHRXw+6Q+AEAc/vF0 EPl42DPAewwM2iF7pau+1vOXd+zeS+D3OkDkl++6rbkITaXSLX4ZX8kR8Q/qD1N2pgQJ h0TtKGZbZ1TLLp1LFZ33O1s1gJznmbM+yerqW2AL68K3JYj0qjeTRnZjBDYBQVKs3Iq8 +cky8e69DUR9Krk6czti9QUGb7RIRuCBPAs+fPgoWpmmjLANu8S49m8R/11p+bL4wEdD gKNg== 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=Wq8SgS+S++92WjdxAtu+TjrAUKELKI7lQyCPDnPOKtk=; b=dmrtmPt52hcK4H7LKJ3SgSQkHm5TY+QQUBJQztCRFharf+izZQnyHtMCSAbrxIeZvN 9OIjEPjQf8PAZwTRO/5WfYtqpS3V2rn0Za5ZnX3WcxSHEUqnORafqCit9gBVeLJeGYFn +9vcX65a5aqyf7DGRRGaAxbu7U9SpXkbUEguSrQpMmKHtgY/YgnERIjiV//LzC6oqbkb 8G4vcYp2l3g3/rA9871vW2JxNcLOEv81RWaVcLrvtwz+xChWeh1w/AxK+UuCE0qMZKTR +g+ootBrfFVkYSrFwd8Bsw+XSLn3s8FdVyTDz6oB0S0maaMcCM4yWvHhF7Fq4Iz6jFHp agJQ== X-Gm-Message-State: APjAAAW313dNx1KsgfibUIG5k3cdOMlpoQiCPi6naVfovFrAxIinCzK5 0B5XUphOvvRmZtcAovUhmd/Odg== X-Google-Smtp-Source: APXvYqwUzmxKl6yxvlEvDaJcG5ifhuWhGcLxGsbFcM5PaK8F/ptRLNDtdxHRrGvVQFCbPgVz9jEv6w== X-Received: by 2002:adf:e550:: with SMTP id z16mr3777520wrm.5.1581366495296; Mon, 10 Feb 2020 12:28:15 -0800 (PST) Received: from localhost.localdomain (ipb21a6b30.dynamic.kabel-deutschland.de. [178.26.107.48]) by smtp.gmail.com with ESMTPSA id w13sm2009994wru.38.2020.02.10.12.28.13 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 10 Feb 2020 12:28:14 -0800 (PST) Message-ID: <8f78df8238b7d367b8fb8c869b2f9d3fc2d01813.camel@cybertec.at> Subject: Re: PITR for one database in cluster From: Laurenz Albe To: Vijay Ganji , pgsql-novice@lists.postgresql.org Date: Mon, 10 Feb 2020 21:28:10 +0100 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 Mon, 2020-02-10 at 13:00 -0600, Vijay Ganji wrote: > I am novice to Postgres and I come from db2 world > I want to do Online backup (with archiving) of single database in a cluster and use it for PITR. so i do not have to disturb other databases in the cluster. > I am reading everywhere it is not possible. > I see the solution is to create database cluster for each database, is this the only solution. Yes, that is what you will have to do. Yours, Laurenz Albe -- Cybertec | https://www.cybertec-postgresql.com