Re: Ignore lost+found when checking if a directory is empty
| От | Jeff Davis |
|---|---|
| Тема | Re: Ignore lost+found when checking if a directory is empty |
| Дата | |
| Msg-id | 1312920206.20479.7.camel@jdavis-ux.asterdata.local обсуждение исходный текст |
| Ответ на | Ignore lost+found when checking if a directory is empty (Brian Pitts <bdp@uga.edu>) |
| Ответы |
Re: Ignore lost+found when checking if a directory is empty
|
| Список | pgsql-hackers |
On Tue, 2011-08-09 at 14:52 -0400, Brian Pitts wrote: > When an ext2, ext3, or ext4 filesystem is mounted directly on the > PGDATA directory, initdb will refuse to run because it sees 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 In the referenced discussion (10 years ago), Tom seemed OK with it and Peter did not seem to like it much. I think I agree with Peter here that it's not a very good idea, and I don't see a big upside. With tablespaces it seems to make a little bit more sense, but I'd still lean away from that idea. Regards,Jeff Davis
В списке pgsql-hackers по дате отправления: