Thanks your reply.
I understand what you mean and have tried to correct this patch.
According to the previous use case, the result obtained is as follows:
id | name | year | xmax | xmin | ctid
+--+--+--+--+---
1 | liuwei | 20 | 0 |
859 | (0,1)
Hi??hackers
I may have discovered another issue in the concurrency scenario of
merge, and I am currently not sure if this new issue is related to the
previous one.
It seems that it may also be an issue with the EPQ mechanism in the merge
scenario?
I will provide this test case, hoping it
Hi all,
When I read the source code file src/backend/access/transam/xloginsert.c, I get
something confused me.
In the function XLogSaveBufferForHint, the flags are always REGBUF_FORCE_IMAGE
which means it is always need backups.
Is it right? Why do not check the full_page_writes?
--
Zhang W
Thank you for reply.
You are right and the PostgreSQL server writes the entire content of each disk
page to WAL during the first modification of that page after a
checkpoint while data checksum is on.
But I wonder whether it is necessary or not while my file system can protect
the blocks of d
