Tom,
Thank you for your comments, they are very much appreciated.
You are correct that the transactions are typically short, likely with
dozens of rows.
Do you know of any problems or defects in this area?
Would there be any usefulness to generating Postgres log files?
Once again, thanks for y
Tim Slechta writes:
> The test data below is from a non-virtualized (client system and database
> server) Postgres 14 environment, with no replication, no high availability,
> and with no load balancing. This environment has older and slower disk
> drives, and the test is driven by a single client
The test data below is from a non-virtualized (client system and database
server) Postgres 14 environment, with no replication, no high availability,
and with no load balancing. This environment has older and slower disk
drives, and the test is driven by a single client process.
In this case 24%
Hello
This block is reading and checking the visibility map, I think. We don't have
to check the visibility map during the index scan - we still need to get a
tuple from the table, we can check the visibility for current transaction
there. With index only scan, we need to check the visibility m
