Fresh initdb contains a few deleted B-Tree pages

From: Peter Geoghegan <pg(at)heroku(dot)com>
To: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Fresh initdb contains a few deleted B-Tree pages
Date: 2014-06-30 22:10:14
Message-ID: CAM3SWZRJFLRMohRUpoVeKtSBwR9h9taQyETNVRv6s8Mu--gMiw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I would like to put on the record that there are a few deleted B-Tree
pages in a freshly initdb'd database. As my btreecheck tools shows:

mgd=# select bt_index_verify(indexrelid::regclass::text) from pg_index;
NOTICE: 00000: page 12 of index "pg_attribute_relid_attnam_index" is deleted
LOCATION: bt_page_verify_worker, btreecheck.c:206
NOTICE: 00000: page 13 of index "pg_attribute_relid_attnam_index" is deleted
LOCATION: bt_page_verify_worker, btreecheck.c:206
NOTICE: 00000: page 14 of index "pg_attribute_relid_attnam_index" is deleted
LOCATION: bt_page_verify_worker, btreecheck.c:206
NOTICE: 00000: page 9 of index "pg_attribute_relid_attnum_index" is deleted
LOCATION: bt_page_verify_worker, btreecheck.c:206

(contrib/pageinspect's bt_page_items() will show a similar message if
this is done manually)

This is not a new-to-9.4 issue. I am not suggesting that it's a real
problem that requires immediate fixing, but it is suboptimal. We may
wish to fix this someday.

--
Peter Geoghegan

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2014-06-30 22:17:37 Re: TODO : Allow parallel cores to be used by vacuumdb [ WIP ]
Previous Message Jeff Janes 2014-06-30 22:00:44 Re: TODO : Allow parallel cores to be used by vacuumdb [ WIP ]