Re: "page is not marked all-visible" warning in regression tests

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: "page is not marked all-visible" warning in regression tests
Дата
Msg-id 692.1338905924@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: "page is not marked all-visible" warning in regression tests  (Andres Freund <andres@2ndquadrant.com>)
Ответы Re: "page is not marked all-visible" warning in regression tests  (Andres Freund <andres@2ndquadrant.com>)
Список pgsql-hackers
Andres Freund <andres@2ndquadrant.com> writes:
> On Tuesday, June 05, 2012 03:32:08 PM Tom Lane wrote:
>> I got this last night in a perfectly standard build of HEAD:
>> + WARNING:  page is not marked all-visible but visibility map bit is set in
>> relation "pg_db_role_setting" page 0 --

> 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 ...

Hmm ... from memory, what I did was

configure/build/install from a fresh pull
initdb
start postmaster, fsync off
make installcheck
stop postmaster
apply Hanada-san's json patch, replace postgres executable
start postmaster, fsync off
make installcheck

and it was the second of these runs that failed.  Could we be missing
flushing some blocks out to disk at shutdown?  Maybe fsync off is a
contributing factor?
        regards, tom lane


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Bruce Momjian
Дата:
Сообщение: Time for pgindent run?
Следующее
От: Tom Lane
Дата:
Сообщение: Re: Time for pgindent run?