On Tue, Jun 13, 2017 at 04:07:48PM -0400, Bruce Momjian wrote:
> On Fri, Jun 9, 2017 at 07:55:55AM -0700, Adrian Klaver wrote:
> I apologize for not being smarter on this thread. When I helped with
> the Windows port, I was told Windows didn't have hard links for use by
> tablespace directories,
On Wed, Jun 14, 2017 at 09:59:04AM +0200, Klaus P. Pieper wrote:
> > -Ursprüngliche Nachricht-
> >
> > I apologize for not being smarter on this thread. When I helped with the
> > Windows port, I was told Windows didn't have hard links for use by
> tablespace
> > directories, so I got it
> -Ursprüngliche Nachricht-
>
> I apologize for not being smarter on this thread. When I helped with the
> Windows port, I was told Windows didn't have hard links for use by
tablespace
> directories, so I got it into my head that Windows didn't have hard links.
> Therefore, when I was wri
On Fri, Jun 9, 2017 at 07:55:55AM -0700, Adrian Klaver wrote:
> On 06/09/2017 07:39 AM, Arnaud L. wrote:
> >See this page for more details :
> >http://cects.com/overview-to-understanding-hard-links-junction-points-and-symbolic-links-in-windows/
> >
> >
> >Under "Hard Link (Linking for individual f
On Fri, 9 Jun 2017 07:24:03 -0700, Adrian Klaver
wrote:
>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.
You can make either hard links or symlinks to files. Junctions are
dis
On Fri, 9 Jun 2017 10:07:24 -0400, 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 mistak
Le 9/06/2017 à 17:02, Arnaud L. a écrit :
Le 9/06/2017 à 16:55, Adrian Klaver a écrit :
On 06/09/2017 07:39 AM, Arnaud L. wrote:
So maybe pg_upgrade uses hard-links (i.e. to files), and only the
documentation is wrong by calling them junctions (i.e. soft links to
files) ?
Looks that way. In
Le 9/06/2017 à 16:55, Adrian Klaver a écrit :
On 06/09/2017 07:39 AM, Arnaud L. wrote:
So maybe pg_upgrade uses hard-links (i.e. to files), and only the
documentation is wrong by calling them junctions (i.e. soft links to
files) ?
Looks that way. In file.c in ~/src/bin/pg_upgrade I see:
#ifd
On 06/09/2017 07:39 AM, Arnaud L. wrote:
Le 9/06/2017 à 16:07, Bruce Momjian a écrit :
I was told junction points on Windows were hard links and no one has
ever complained about not being able to remove them.
Sorry, I think my explanation was not very clear.
You can remove the link, but the po
Le 9/06/2017 à 16:07, Bruce Momjian a écrit :
I was told junction points on Windows were hard links and no one has
ever complained about not being able to remove them.
Sorry, I think my explanation was not very clear.
You can remove the link, but the point is to remove the target (i.e. the
old
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
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
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 r
13 matches
Mail list logo