Re: BUG #16799: postgresql log issue(last completed transaction was at log time)

Поиск
Список
Период
Сортировка
От oleg9301 xz
Тема Re: BUG #16799: postgresql log issue(last completed transaction was at log time)
Дата
Msg-id CAFyBvAiZh2EHHzfnfuNnuJRNTd4hmtmVpAJHOA7YiYtwP6XBcw@mail.gmail.com
обсуждение исходный текст
Ответ на Re: BUG #16799: postgresql log issue(last completed transaction was at log time)  (Tom Lane <tgl@sss.pgh.pa.us>)
Ответы Re: BUG #16799: postgresql log issue(last completed transaction was at log time)
Список pgsql-bugs
Дерево обсуждения
There is always transations to commit, I(barman) do pg_basebackup once a day, and recieve wal with pg_receivewal(standby slot). And everything is fine, i have all data on OLAP DB(restore 6 times in day)
(all WAL files playing correctly).


чт, 31 дек. 2020 г. в 18:21, Tom Lane <tgl@sss.pgh.pa.us>:
PG Bug reporting form <noreply@postgresql.org> writes:
> After recovering postgresql from barman, in version 12.5 I don't have next
> string
> "last completed transaction was at log time %s"
> In postgresql 11.9-1.pgdg100+1 everything fine.

I don't see any reason to believe there's a bug here.  That message
would only appear if at least one transaction commit or abort record was
replayed from WAL, and it's quite possible there wouldn't have been.

                        regards, tom lane

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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: BUG #16799: postgresql log issue(last completed transaction was at log time)
Следующее
От: Tom Lane
Дата:
Сообщение: Re: BUG #16799: postgresql log issue(last completed transaction was at log time)