Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dJKpe-0006Vq-UX for pgsql-general@arkaria.postgresql.org; Fri, 09 Jun 2017 14:24:11 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dJKpe-0000Fi-Ac for pgsql-general@arkaria.postgresql.org; Fri, 09 Jun 2017 14:24:10 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dJKpc-0000Ej-WA for pgsql-general@postgresql.org; Fri, 09 Jun 2017 14:24:09 +0000 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dJKpa-0006Gs-4k for pgsql-general@postgresql.org; Fri, 09 Jun 2017 14:24:07 +0000 Received: from compute6.internal (compute6.nyi.internal [10.202.2.46]) by mailout.nyi.internal (Postfix) with ESMTP id 55C8420990; Fri, 9 Jun 2017 10:24:05 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute6.internal (MEProxy); Fri, 09 Jun 2017 10:24:05 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=fm1; bh=jJKvN2nGjJoZ9sgAP5 IZcaFjiNBjOmCUxzg9H4OBJOM=; b=UFPkk91IpTHea+Y+nS814dFTne8sAbe3i8 JKgMmh1AI7SxO/D2RCgNPn4TG3wNp1e9dS1Yp8l9F1AQPXsrG15+2Ay+DMXi5SDB ghJ3PEOl7i8hc/Wh7aHmk1onpDldCSqzhLqC4jVnASgia5Y/DAwyGOuiJdHtNN5+ i8OU9Ildfl7plgRNFKXkNWDFTY2rN1cfP6YyRGVc+XHheRyDdZ6HxjCytQhMzKFC aXuszPEggq8ZSgwdKSEWwY859JtdGI2Qm747K1LqPEDJBLodAAwODqrWygiJKGuw t9lnskTIn5IXSe31M4huhoGkWCKEDdjXjsabTCh+bdHAFZCNLXog== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= fm1; bh=jJKvN2nGjJoZ9sgAP5IZcaFjiNBjOmCUxzg9H4OBJOM=; b=RKcZJjqx 7p8me9Rc18fZzx8iglnhIwnP0Lptk8Ap7Fpkcn6xl3pom7fDI5JfgDWf75/3nQyj opBUnRyZe7IVKsjDu55gRxfQ28qlAJ4D7y2pwWkZl6nIZS+FWAGt86GNRxC9NPTz g5ATSDKJ/rISkHNeQYeCBxNR1FIX/N9FB4rDWrYLE/Xn76jC7dyieGT3EHQCZlU3 o/iZ1h83ZboioJWe68K3GEsrLOkYvcSckrhivywc09VweU4hIgNgXwkRhbyfWV8E r+MbU3nwX6h9HEgc2xmAjMEPyXRzB4dcv1AjMhUx4EkaHmQkN1n4hg/zMDq8aPPQ PunNvpwYdj4Yng== X-ME-Sender: X-Sasl-enc: 6YlZtXNVemZqwa/F6xtaIYNcxgLKmTKRnpM6/WTJmSRW 1497018245 Received: from [192.168.1.2] (75-172-126-41.tukw.qwest.net [75.172.126.41]) by mail.messagingengine.com (Postfix) with ESMTPA id B400D7E6E5; Fri, 9 Jun 2017 10:24:04 -0400 (EDT) Subject: Re: pg_upgrade --link on Windows To: Bruce Momjian , "Arnaud L." Cc: PG-General Mailing List References: <8da3dbd9-7daf-5589-0cc8-0eede930a492@codata.eu> <20170609140724.GB21215@momjian.us> From: Adrian Klaver Message-ID: <6a638c60-90bb-4921-8ee4-5fdad68f8b09@aklaver.com> Date: Fri, 9 Jun 2017 07:24:03 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: <20170609140724.GB21215@momjian.us> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -2.7 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-general Precedence: bulk Sender: pgsql-general-owner@postgresql.org On 06/09/2017 07:07 AM, Bruce Momjian wrote: > On Fri, Jun 9, 2017 at 12:00:56PM +0200, Arnaud L. wrote: >> Hi >> >> The pg_upgrade documentation for PostgreSQL 9.6 states that --link will use >> junction points on Windows. >> Shouldn't it rather user hard-links ? >> If I'm not mistaken, with junction points (i.e. soft-links to directories), >> the old data dir cannot be removed. >> With hard-links to file, we can get rid of the old data dir once we are sure >> that the upgrade is fine. > > I was told junction points on Windows were hard links and no one has > ever complained about not being able to remove them. > https://msdn.microsoft.com/en-us/library/windows/desktop/aa365006(v=vs.85).aspx Seems to me the difference is hard links point to file, junctions to directories. So if I am following: https://en.wikipedia.org/wiki/NTFS_junction_point#Creating_or_deleting_a_junction_point You remove the junction and then the directory it points to. -- Adrian Klaver adrian.klaver@aklaver.com -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general