Ignore lost+found when checking if a directory is empty

Поиск
Список
Период
Сортировка
От Brian Pitts
Тема Ignore lost+found when checking if a directory is empty
Дата
Msg-id 4E4181E9.2010902@uga.edu
обсуждение исходный текст
Ответы Re: Ignore lost+found when checking if a directory is empty  (Jeff Davis <pgsql@j-davis.com>)
Re: Ignore lost+found when checking if a directory is empty  (Jaime Casanova <jaime@2ndquadrant.com>)
Re: Ignore lost+found when checking if a directory is empty  (Jeff Davis <pgsql@j-davis.com>)
Re: Ignore lost+found when checking if a directory is empty  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
When an ext2, ext3, or ext4 filesystem is mounted directly on the PGDATA directory, initdb will refuse to run because
itsees the 
lost+found directory that mke2fs created and assumes the PGDATA directory is already in use for something other than
PostgreSQL.
Attached is a patch against master which will cause a directory that contains only lost+found to still be treated as
empty.

This was previously proposed in 2001; see http://archives.postgresql.org/pgsql-hackers/2001-03/msg01194.php

--
Brian Pitts
Systems Administrator | EuPathDB Bioinformatics Resource Center
706-542-1447 | bdp@uga.edu | http://eupathdb.org

Вложения

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

Предыдущее
От: Florian Pflug
Дата:
Сообщение: Re: augmenting MultiXacts to improve foreign keys
Следующее
От: Alvaro Herrera
Дата:
Сообщение: Re: augmenting MultiXacts to improve foreign keys