Re: PostgreSQL, NetBSD and NFS - Mailing list pgsql-hackers

From Tom Lane
Subject Re: PostgreSQL, NetBSD and NFS
Date
Msg-id 26882.1044463796@sss.pgh.pa.us
Whole thread Raw
In response to Re: PostgreSQL, NetBSD and NFS  ("D'Arcy J.M. Cain" <darcy@druid.net>)
Responses Re: PostgreSQL, NetBSD and NFS  ("D'Arcy J.M. Cain" <darcy@druid.net>)
Re: PostgreSQL, NetBSD and NFS  (Justin Clift <justin@postgresql.org>)
List pgsql-hackers
"D'Arcy J.M. Cain" <darcy@druid.net> writes:
> Hmm.  This time it passed that point but this happened:

> COPY "certificate" FROM stdin;
> NOTICE:  copy: line 253677, bt_insertonpg[certificate_pkey]: parent page 
> unfound - fixing branch
> ERROR:  copy: line 253677, bt_fixlevel[certificate_pkey]: invalid item 
> order(1) (need to recreate index)

Hoo boy.  I was already suspecting data corruption in the index, and
this looks like more of the same.  My thoughts are definitely straying
in the direction of "the NFS server is dropping bits, somehow".

Both this and the (admittedly unproven) bt_moveright loop suggest
corrupted values in the cross-page links that exist at the very end of
each btree index page.  I wonder if it is possible that, every so often,
you are losing just the last few bytes of an NFS transfer?
        regards, tom lane


pgsql-hackers by date:

Previous
From: "D'Arcy J.M. Cain"
Date:
Subject: Re: PostgreSQL, NetBSD and NFS
Next
From: wade
Date:
Subject: Re: POSIX regex performance bug in 7.3 Vs. 7.2