Skip site navigation (1) Skip section navigation (2)

Re: win32 inode fix

From: Neil Conway <neilc(at)samurai(dot)com>
To: Claudio Natoli <claudio(dot)natoli(at)memetrics(dot)com>
Cc: pgsql-patches(at)postgresql(dot)org
Subject: Re: win32 inode fix
Date: 2004-02-09 02:06:26
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-patches
Claudio Natoli <claudio(dot)natoli(at)memetrics(dot)com> writes:
> Under Win32, stat() returns an st_ino field, but it has no meaning (on
> Win2K, and possibly all Win32 variants, it is always 0).

MSDN says:

    Number of the information node (the inode) for the file
    (UNIX-specific). On UNIX file systems, the inode describes the
    file date and time stamps, permissions, and content. When files
    are hard-linked to one another, they share the same inode. The
    inode, and therefore st_ino, has no meaning in the FAT, HPFS, or
    NTFS file systems.

I wonder if this might return non-zero for some relatively rare Win32
filesystems (say, an NFS share mounted via MS Services For
Unix). Perhaps it might be cleaner to consider a zero inode "unknown",
and therefore not equal to anything else?

-Neil (who knows next to nothing about Win32, so take that with a
grain of salt)

In response to

pgsql-patches by date

Next:From: Tom LaneDate: 2004-02-09 06:25:10
Subject: Re: [HACKERS] dollar quoting
Previous:From: Simon RiggsDate: 2004-02-08 23:29:47
Subject: Re: [PATCHES] update i386 spinlock for hyperthreading

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group