Re: BUG #7634: Missing files in global/ after a lot of CREATE DATABASE / DROP DATABASE
От | Tom Lane |
---|---|
Тема | Re: BUG #7634: Missing files in global/ after a lot of CREATE DATABASE / DROP DATABASE |
Дата | |
Msg-id | 4225.1351794039@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | BUG #7634: Missing files in global/ after a lot of CREATE DATABASE / DROP DATABASE (thomas.eckestad@gmail.com) |
Ответы |
Re: BUG #7634: Missing files in global/ after a lot of CREATE
DATABASE / DROP DATABASE
|
Список | pgsql-bugs |
thomas.eckestad@gmail.com writes: > After a couple of days/weeks with frequent unit test activity DROP DATABASE > eventually triggers errors on the following form: > 2012-05-08 08:53:02.512 CEST> LOG: statement: DROP DATABASE IF EXISTS > "HEAD_test_migrate_group_data_10010018668" > 2012-05-08 08:53:02.512 CEST> ERROR: could not open file "global/12693": No > such file or directory > 2012-05-08 08:53:02.512 CEST> STATEMENT: DROP DATABASE IF EXISTS > "HEAD_test_migrate_group_data_10010018668" That is extremely peculiar --- AFAICS, 9.1 should never assign a relfilenode of 12693. (OIDs assigned by initdb don't get past about 11900 in that version, and OIDs assigned after normal postmaster start should always be above 16384.) Is it always exactly "global/12693" that's complained of? Could you monitor the contents of $PGDATA/global and see if the set of filenames present changes while you're running these tests? regards, tom lane
В списке pgsql-bugs по дате отправления: