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

Поиск
Список
Период
Сортировка
От Jerry Sievers
Тема Re: recovery.conf not getting changed to recovery.done after PITR
Дата
Msg-id 871sa6y72t.fsf@jsievers.enova.com
обсуждение исходный текст
Ответ на recovery.conf not getting changed to recovery.done after PITR  (amit tripathi <amittripathi1445@gmail.com>)
Ответы Re: recovery.conf not getting changed to recovery.done after PITR
Список pgsql-admin
amit tripathi <amittripathi1445@gmail.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.consulting@comcast.net
p: 312.241.7800


В списке pgsql-admin по дате отправления:

Предыдущее
От: Andrey Zhidenkov
Дата:
Сообщение: Determine which query prevents applying WALs on standby
Следующее
От: Jerry Sievers
Дата:
Сообщение: Re: Determine which query prevents applying WALs on standby