pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Ron <ronljohnsonjr@gmail.com>
To: pgsql-general@lists.postgresql.org
Subject: Re: PITR partial timing
Date: Tue, 17 Oct 2023 08:39:35 -0500
Message-ID: <f06f1af3-0a15-4908-a3e1-5a05e0ac0a23@gmail.com> (raw)
In-Reply-To: <CAJWX+EMOEFa+NERn3E+3C7RKroUGi3-aQF_OoWxYBoMdOCFzLg@mail.gmail.com>
References: <CAJWX+EMOEFa+NERn3E+3C7RKroUGi3-aQF_OoWxYBoMdOCFzLg@mail.gmail.com>

Don't write your own PITR.  Use PgBackRest, barman, etc.

On 10/16/23 12:08, Rama Krishnan wrote:
> Hi team,
>
> I  m testing PITR
>
> 1.if I am doing full recovery what ever the new tables were create will 
> not be appear how to handle it
>
> 2. I have given my logs which time log I have to choose for PITR partial 
> recovery
>
>
> 2023-10-16 16:22:35 UTC [16561]: [13-1] user=postgres,db=postgresLOG: 
>  statement: create database pumastore;
> 2023-10-16 16:22:35 UTC [16561]: [14-1] user=postgres,db=postgresLOG: 
>  duration: 70.433 ms
> 2023-10-16 16:23:02 UTC [16561]: [15-1] user=postgres,db=postgresLOG: 
>  statement: CREATE TABLE categories (
>    category integer NOT NULL,
>    categoryname character varying(50) NOT NULL
> );
> 2023-10-16 16:23:02 UTC [16561]: [16-1] user=postgres,db=postgresLOG: 
>  duration: 6.328 ms
> 2023-10-16 16:23:28 UTC [16561]: [17-1] user=postgres,db=postgresLOG: 
>  statement: COPY categories (category, categoryname) FROM stdin;
> 2023-10-16 16:23:41 UTC [16561]: [18-1] user=postgres,db=postgresLOG: 
>  duration: 12695.122 ms
> 2023-10-16 16:23:52 UTC [16561]: [19-1] user=postgres,db=postgresLOG: 
>  statement: table categories;
> 2023-10-16 16:23:52 UTC [16561]: [20-1] user=postgres,db=postgresLOG: 
>  duration: 0.573 ms
> 2023-10-16 16:24:20 UTC [16561]: [21-1] user=postgres,db=postgresLOG: 
>  statement: select pg_switch_wal();
> 2023-10-16 16:24:20 UTC [16561]: [22-1] user=postgres,db=postgresLOG: 
>  duration: 61.904 ms
>
> 2023-10-16 16:26:25 UTC [16561]: [23-1] user=postgres,db=postgresLOG: 
>  statement: drop table categories;
> 2023-10-16 16:26:25 UTC [16561]: [24-1] user=postgres,db=postgresLOG: 
>  duration: 5.165 ms
>

-- 
Born in Arizona, moved to Babylonia.

view thread (2+ messages)

Message-ID: <f06f1af3-0a15-4908-a3e1-5a05e0ac0a23@gmail.com>
Permalink:  ../f06f1af3-0a15-4908-a3e1-5a05e0ac0a23@gmail.com/
Also on:    postgresql.org/message-id/f06f1af3-0a15-4908-a3e1-5a05e0ac0a23@gmail.com

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-general@postgresql.org
  Cc: ronljohnsonjr@gmail.com
  Subject: Re: PITR partial timing
  In-Reply-To: <f06f1af3-0a15-4908-a3e1-5a05e0ac0a23@gmail.com>
  References: <CAJWX+EMOEFa+NERn3E+3C7RKroUGi3-aQF_OoWxYBoMdOCFzLg@mail.gmail.com> <f06f1af3-0a15-4908-a3e1-5a05e0ac0a23@gmail.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox