Re: PITR partial timing

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.