From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
---|---|
To: | MauMau <maumau307(at)gmail(dot)com> |
Cc: | Asif Naeem <anaeem(dot)it(at)gmail(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [bug fix] PostgreSQL fails to start on Windows if it crashes after tablespace creation |
Date: | 2014-03-21 07:26:42 |
Message-ID: | CAA4eK1Jdw-ve9j8f1RS61CZZZRKp1PBQ2M3mKjj_qLumtukKRA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, Mar 21, 2014 at 12:24 PM, MauMau <maumau307(at)gmail(dot)com> wrote:
> From: "Amit Kapila" <amit(dot)kapila16(at)gmail(dot)com>
>> If create_tablespace_directories() needs to handle with directory both on
>> Windows/Linux, then shouldn't it be a runtime check as in your first
>> version rather than compile time check?
>> Also isn't that the reason why destroy_tablespace_directories() have
>> similar
>> check?
>
>
> I see..., and you are correct. The first version of my patch should be the
> right fix. It seems that my head went somewhere when I submitted the second
> revision.
>
> What should I do? Should I re-submit the first revision as the latest fifth
> revision and link the email from the CommitFest newest entry?
The comments in your first version needs to be improved, as there
you just mentioned a Windows specific comment:
+ /* On Windows, lstat()
I think you can change comments (make it somewhat similar to
destroy_tablespace_directories) and then submit it as a new version.
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Dilip kumar | 2014-03-21 07:48:56 | Re: TODO : Allow parallel cores to be used by vacuumdb [ WIP ] |
Previous Message | Peter Geoghegan | 2014-03-21 07:23:10 | Re: jsonb and nested hstore |