Hello, pgsql-hackers
I'm gathering information about the following error.
FATAL: could not access status of transaction ..
DETAIL: Could not read from file (pg_clog/ or pg_xact/) ...: Success.
This error has caused the server to fail to start with recovery.
I got a report that it happe
On Thu, 21 Nov 2019 10:40:36 +0100
Peter Eisentraut wrote:
> On 2019-11-21 02:42, TAKATSUKA Haruka wrote:
> > FATAL: could not access status of transaction ..
> > DETAIL: Could not read from file (pg_clog/ or pg_xact/) ...:
> > Success.
> >
> > Th
Hello,
I'm a hamerkop maintainer.
Sorry I have missed the scm error for so long.
Today I switched scmrepo from git.postgresql.org/git/postgresql.git
to github.com/postgres/postgres.git and successfully modernized
the build target code.
with best regards, Haruka Takatsuka
On Thu, 16 May 2024 1
On Wed, 23 Jul 2025 23:00:00 +0300
Alexander Lakhin wrote:
{snip}
> >>> Nagata-san, could you please share the configuration of hamerkop? If it's
> >>> running inside VM, what virtualization software is used?
> > It's vmware ESXi 7.0.3 (21930508).
> > This Windows enable auto-synchronize with '
Hello Alexander,
On Wed, 23 Jul 2025 00:55:37 +
Yugo Nagata - Buildfarm wrote:
> > Nagata-san, could you please share the configuration of hamerkop? If it's
> > running inside VM, what virtualization software is used?
It's vmware ESXi 7.0.3 (21930508).
This Windows enable auto-synchronize
