Re: Reviewing freeze map code

On 2016-06-09 19:33:52 -0700, Andres Freund wrote:
> I played with it for a while, and besides
> finding intentionally caused corruption, it didn't flag anything
> (besides crashing on a standby, as in 2)).

Ugh. Just sends after I sent that email:
      oid        |    t_ctid    
------------------+--------------pgbench_accounts | (889641,33)pgbench_accounts | (893854,56)pgbench_accounts |
(924226,13)pgbench_accounts| (1073457,51)pgbench_accounts | (1084904,16)pgbench_accounts | (1111996,26)
 
(6 rows)
oid | t_ctid 
-----+--------
(0 rows)
      oid        |    t_ctid    
------------------+--------------pgbench_accounts | (739198,13)pgbench_accounts | (887254,11)pgbench_accounts |
(1050391,6)pgbench_accounts| (1158640,46)pgbench_accounts | (1238067,18)pgbench_accounts | (1273282,22)pgbench_accounts
|(1355816,54)pgbench_accounts | (1361880,33)
 
(8 rows)
oid | t_ctid 
-----+--------
(0 rows)

Seems to be correlated with a concurrent vacuum, but it's hard to tell,
because I didn't have psql output a timestamp.

Greetings,

Andres Freund