Re: recovery.conf not getting changed to recovery.done after PITR

From: Jerry Sievers <gsievers19(at)comcast(dot)net>
To: amit tripathi <amittripathi1445(at)gmail(dot)com>
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: recovery.conf not getting changed to recovery.done after PITR
Date: 2018-09-06 15:32:58
Message-ID: 871sa6y72t.fsf@jsievers.enova.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

amit tripathi <amittripathi1445(at)gmail(dot)com> writes:

> Hi All,
>
> Need help on below issue.
>
>>In recovery.conf file if we give recovery_target_time as  2018-09-05
> 09:54:21 (without EST)  and restart the postgresql, recovery.conf is
> not getting changed to recovery.done. Although PITR is successful and
> only till given time records/tables are restored. But database goes
> in recovery mode and i am unable to enter more records.

Show us your recovery.conf after masking anything sensitive.

You probably are paused at a recovery target and if trying to promote
the pitr cluster at this point, need to un-pause replication else it
will not respond to the promote.

HTH

>
>>In the second case if i add EST and restart the postgresql,
> recovery.conf is getting changed to recovery.done but everything is
> getting restored. I mean tables/records added after 2018-09-05
> 09:54:21 are also restored.
>
> Other information-Doing it on Linux host. Timezone in postgresql.conf
> is US/Eastern.
>
>
> Regards,
> Amit
>
>

--
Jerry Sievers
Postgres DBA/Development Consulting
e: postgres(dot)consulting(at)comcast(dot)net
p: 312.241.7800

In response to

Responses

Browse pgsql-admin by date

  From Date Subject
Next Message Jerry Sievers 2018-09-06 15:35:05 Re: Determine which query prevents applying WALs on standby
Previous Message Andrey Zhidenkov 2018-09-06 12:09:41 Determine which query prevents applying WALs on standby