Re: [bug fix] PostgreSQL fails to start on Windows if it crashes after tablespace creation

From: "MauMau" <maumau307(at)gmail(dot)com>
To: "Asif Naeem" <anaeem(dot)it(at)gmail(dot)com>
Cc: "Andrew Dunstan" <andrew(at)dunslane(dot)net>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [bug fix] PostgreSQL fails to start on Windows if it crashes after tablespace creation
Date: 2014-02-04 10:47:49
Message-ID: 61C1035D921348B59F199CBEFFBEE67A@maumau
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I'm sorry, I'm replying to an older mail, because I lost your latest mail by
mistake.

> Ah. Sorry, I missed that part. As NTFS junctions and symbolic links are
> different (although they behave similarly), there seems only a minor
> inconvenience related to misleading error message i.e.

You are right. Fixed.

Regards
MauMau

Attachment Content-Type Size
remove_tblspc_symlink_v4.patch application/octet-stream 913 bytes

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message MauMau 2014-02-04 11:28:14 Re: [bug fix] postgres.exe fails to start on Windows Server 2012 due to ASLR
Previous Message Andres Freund 2014-02-04 10:22:03 Re: should we add a XLogRecPtr/LSN SQL type?