From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
Cc: | VMaury <vmaury79(at)yahoo(dot)fr>, pgsql-bugs <pgsql-bugs(at)postgresql(dot)org> |
Subject: | Re: BUG #5725: server couldn't start when installing on liveCD |
Date: | 2010-10-26 02:37:31 |
Message-ID: | AANLkTi=YSy4bCM13JPX00LSNyzqFkf_mSVUf3UmC_8Ot@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Mon, Oct 25, 2010 at 5:43 PM, Alvaro Herrera
<alvherre(at)commandprompt(dot)com> wrote:
> Excerpts from VMaury's message of lun oct 25 15:44:01 -0300 2010:
>
>> This bug has been reported by someone else (in spanish):
>> https://bugs.launchpad.net/ubuntu/+source/postgresql-8.4/+bug/658857
>>
>> However, this install works perfectly once Ubuntu is installed.
>> Why is there a difference between install and live?
>
> Not as far as PostgreSQL is concerned. You should probably take this up
> with the Ubuntu packagers. Perhaps it's a problem with the mount
> options for the filesystem.
>
> Hmm, my manpage says that open() could fail with EINVAL if O_DIRECT is
> used and not supported by the filesystem. We use O_DIRECT in some
> wal_sync_method configurations. Maybe the Ubuntu live is not getting
> that flag right.
>
> I think you should take this up with Martin Pitt, the packager.
If this really is caused by a WAL setting that's incompatible with the
filesystem, maybe we should add a HINT. This makes two reports today,
plus apparently at least one more on the Ubuntu sight.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Heikki Linnakangas | 2010-10-26 07:48:27 | Re: Recovery bug |
Previous Message | Marcus | 2010-10-26 01:43:06 | BUG #5726: Re: BUG #5723: Can not start postgres after install |