Re: Unhelpful initdb error message
От | Thom Brown |
---|---|
Тема | Re: Unhelpful initdb error message |
Дата | |
Msg-id | CAA-aLv5RD9Ebjyp5cnEs0HdJc5jgPWFtX4Dv=mORut0-=YM5KA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Unhelpful initdb error message (Adrian Klaver <adrian.klaver@gmail.com>) |
Ответы |
Re: Unhelpful initdb error message
Re: Unhelpful initdb error message Re: Unhelpful initdb error message |
Список | pgsql-general |
On 6 March 2012 18:01, Adrian Klaver <adrian.klaver@gmail.com> wrote: > On Tuesday, March 06, 2012 9:53:52 am Tom Lane wrote: >> Thom Brown <thom@linux.com> writes: >> > /home/thom/Development/data was causing problems so: >> > >> > mv data databroken >> > mkdir data >> > initdb >> > >> > ... working fine again. I then used the postmaster.pid from this when >> > started up. But if I do: >> > >> > pg_ctl stop >> > rm -rf data >> > mv databroken data >> > initdb >> > >> > ... error messages appear again. >> >> Okay, so the question becomes: what is different between databroken and >> a freshly mkdir'd empty directory? If there is no visible difference in >> contents, ownership, or permissions, then it seems like this is evidence >> of a filesystem bug (ie, apparently empty directory acts nonempty for >> some operations). > > A thought, what if you do rm -rf * in the data directory? I've done that a couple times, but no effect. I think Tom's point about a filesystem bug is probably right. -- Thom
В списке pgsql-general по дате отправления: