Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1dcFai-0002Tc-3A for pgsql-docs@arkaria.postgresql.org; Mon, 31 Jul 2017 18:38:56 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1dcFah-0001c1-Fo for pgsql-docs@arkaria.postgresql.org; Mon, 31 Jul 2017 18:38:55 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dcFaL-0000yE-0e for pgsql-docs@postgresql.org; Mon, 31 Jul 2017 18:38:33 +0000 Received: from out1-smtp.messagingengine.com ([66.111.4.25]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1dcFaH-00060U-BX for pgsql-docs@postgresql.org; Mon, 31 Jul 2017 18:38:32 +0000 Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 02B8C20743; Mon, 31 Jul 2017 14:38:28 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute7.internal (MEProxy); Mon, 31 Jul 2017 14:38:28 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=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=zKNLtNPpAiU8lEC0uRI0jYLB/6LcO0Mx516EyDRa+fE=; b=Cd4xmTwp 0+u+jgmzfR/sc+DINzcIUXJEcpqKYORjFxxhVB0Zfsi+zHsQu6GMXW3YhuhbeDIG MsCsEI6r0TrsFEGH2CWrv42c5QykezmSDRwU2VdmbctMQn6jp7Pz196G1eprzWHM k8iQwZOUXgFwS4fyxdHGBk/swvoYkA70AL5mxWLOwih58F2g5NcRK35lwwhnOzdy 4I+K9oJNhzG8Sa5My0aRW4K/Gfc0dqfPvLE+3f8VT2mLXmu6GnyqkWuuzf2razEi 7AQA++IKpevmeLuxD3g7Tj0PDLIOIliKkwsZxOm8AkojkO6uFjfbAEcNRQHVAeBI sHh36OjVIzvJag== X-ME-Sender: X-Sasl-enc: Tn8j0E1i91H8lBRk9fzy7t70NzyS5ed1nd0tlZQ8GS4l 1501526307 Received: from april.local (c-73-13-66-39.hsd1.pa.comcast.net [73.13.66.39]) by mail.messagingengine.com (Postfix) with ESMTPA id BBF61240B1; Mon, 31 Jul 2017 14:38:27 -0400 (EDT) Subject: Re: does pg_upgrade on Windows use junction points or hard links? To: holger@jakobs.com, pgsql-docs@postgresql.org References: <20170727132455.1449.85825@wrigleys.postgresql.org> From: Peter Eisentraut Organization: 2ndQuadrant Message-ID: <5d2d41b3-50b6-9d7c-5c86-6b2f5534b5ab@2ndquadrant.com> Date: Mon, 31 Jul 2017 14:38:27 -0400 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <20170727132455.1449.85825@wrigleys.postgresql.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-docs Precedence: bulk Sender: pgsql-docs-owner@postgresql.org On 7/27/17 09:24, holger@jakobs.com wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/9.6/static/pgupgrade.html > Description: > > https://www.postgresql.org/docs/9.6/static/pgupgrade.html states that > junction points are created when --link is used. > > https://msdn.microsoft.com/en-us/library/windows/desktop/aa365006(v=vs.85).aspx > says that junction points are "soft links" (symbolic links in Unix speak), > which would be disastrous if the original data directory is being purged > afterwards. > > Is the documentation incorrect? > Is the program correct? It actually uses hard links on Windows as well. The documentation has been fixed and will appear correctly in the next minor releases. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services -- Sent via pgsql-docs mailing list (pgsql-docs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-docs