From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Subject: | Re: "page is not marked all-visible" warning in regression tests |
Date: | 2012-06-05 14:01:28 |
Message-ID: | 201206051601.28668.andres@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tuesday, June 05, 2012 03:32:08 PM Tom Lane wrote:
> I got this last night in a perfectly standard build of HEAD:
>
> *** /home/tgl/pgsql/src/test/regress/expected/sanity_check.out Thu Jan 12
> 14:06:14 2012 ---
> /home/tgl/pgsql/src/test/regress/results/sanity_check.out Mon Jun 4
> 20:28:39 2012 ***************
> *** 1,4 ****
> --- 1,5 ----
> VACUUM;
> + WARNING: page is not marked all-visible but visibility map bit is set in
> relation "pg_db_role_setting" page 0 --
> -- sanity check, if we don't have indices the test will take years to
> -- complete. But skip TOAST relations (since they will have varying
>
> ======================================================================
>
> I didn't manage to reproduce it in a few tries, and I don't recall
> having seen the like reported from the buildfarm either. So there's
> some low-probability bug in there ...
I have seen that twice just yesterday. Couldn't reproduce it so far.
Workload was (pretty exactly):
initdb
postgres -c fsync=off
pgbench -i -s 100
CREATE TABLE data(id serial primary key, data int);
ALTER SEQUENCE data_id_seq INCREMENT 2;
VACUUM FREEZE;
normal shutdown
postgres -c fsync=on
pgbench -c 20 -j 20 -T 100
WARNING: ... pg_depend ...
WARNING: ... can't remember ...
Greetings,
Andres
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2012-06-05 14:08:11 | Time for pgindent run? |
Previous Message | Simon Riggs | 2012-06-05 13:50:02 | Re: Backup docs |