On Sun, Jan 5, 2020 at 11:00 PM chenhj wrote:
> According to above information, the flags of the heap page (163363) with the
> problem tuple (163363, 9) is 0x0001 (HAS_FREE_LINES), that is, ALL_VISIBLE is
> not set.
>
> However, according hexdump content of the corresponding vm file, that
> bl
Hi, all
Our other system had encountered the same failure, but this time it is
PostgreSQL 10.7(rhel 6.3).
Details are as follows:
Phenomenon:
app_db=# select count(*) from loba_sp_cost_xcd_104561;
ERROR: could not access status of transaction 35153545
DETAIL: Could not open file
access status of transaction 389225416
126690 2019-09-03 14:06:52 UTC XX000
DETAIL: Could not read from file
"/1-1/kangda/pgdata/pg_xact/0E7F" at offset 245760: Success.
126690 2019-09-03 14
t;
> lma=# select count(*) from bi_dm.tdm_ttk_site_on_way_rt;
> ERROR: could not access status of transaction 3250922107
> DETAIL: Could not open file "pg_xact/0C1C": No such file or directory.
>
> Here are some related information
>
> Th
bi_dm.tdm_ttk_site_on_way_rt;
ERROR: could not access status of transaction 3250922107
DETAIL: Could not open file "pg_xact/0C1C": No such file or directory.
Here are some related information
The CLOG files in pg_xact diractory is as follow:
0C4A(Last update date:
