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

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: oleg9301(at)gmail(dot)com
Cc: pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #16799: postgresql log issue(last completed transaction was at log time)
Date: 2020-12-31 15:21:35
Message-ID: 2452476.1609428095@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

PG Bug reporting form <noreply(at)postgresql(dot)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

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message oleg9301 xz 2020-12-31 15:33:45 Re: BUG #16799: postgresql log issue(last completed transaction was at log time)
Previous Message PG Bug reporting form 2020-12-31 14:52:58 BUG #16799: postgresql log issue(last completed transaction was at log time)