Daniel Farina <dan...@heroku.com> writes:
> And, even more interestingly,
> $ stat 16587.8 pg_internal.init
> File: `16587.8'
> Size: 98532 Blocks: 200 IO Block: 4096 regular file
> Device: fe00h/65024d Inode: 1073741952 Links: 1
> Access: (0600/-rw-------) Uid: ( 107/postgres) Gid: ( 115/postgres)
> Access: 2011-12-14 23:35:35.630043643 +0000
> Modify: 2011-12-14 23:35:35.630043643 +0000
> Change: 2011-12-14 23:35:35.630043643 +0000
> File: `pg_internal.init'
> Size: 98532 Blocks: 200 IO Block: 4096 regular file
> Device: fe00h/65024d Inode: 1073741952 Links: 1
> Access: (0600/-rw-------) Uid: ( 107/postgres) Gid: ( 115/postgres)
> Access: 2011-12-14 23:35:35.630043643 +0000
> Modify: 2011-12-14 23:35:35.630043643 +0000
> Change: 2011-12-14 23:35:35.630043643 +0000
> Most notably, the inode numbers are the same. At first, I thought
> this was a file descriptor race in PG, but then I noticed the file
> system only reports *one* link: that doesn't look like a valid state
> for XFS.
Yeah. In any case it wouldn't be a PG bug, because we don't issue any
link(2) calls AFAIR. File an XFS bug.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
