> >> CREATE INDEX hash_i4_index ON hash_i4_heap USING hash (random int4_ops); > >> + ERROR: cannot read block 3 of hash_i4_index: Bad address > > "Bad address"? That seems pretty bizarre. This is obviously something that shows up on _some_ NetBSD platforms. The above was on sparc64, but that same problem is the only one I see that Bad address message was actually from sparc. ---------------------------(end of broadcast)--------------------------- TIP 6: Have you searched our list archives? http://www.postgresql.org/search.mpl
- Re: [lockhart@alumni.caltech.edu: [HACKERS] Third call ... Thomas Lockhart
- Re: [lockhart@alumni.caltech.edu: [HACKERS] Third ... Tom Lane
- Re: [lockhart@alumni.caltech.edu: [HACKERS] Th... Tom Ivar Helbekkmo
- Re: [lockhart@alumni.caltech.edu: [HACKERS... Tom Lane
- NetBSD "Bad address" failure (wa... matthew green
- NetBSD "Bad address" failure (wa... Tom Lane
- Re: NetBSD "Bad address" fai... Tom Lane
- Re: NetBSD "Bad address"... Tom Ivar Helbekkmo
- Re: NetBSD "Bad address&... Tom Lane
- re: NetBSD "Bad address" fai... matthew green
- re: [lockhart@alumni.caltech.edu: [HACKERS] Th... matthew green
- re: [lockhart@alumni.caltech.edu: [HACKERS] Th... matthew green
- Re: [lockhart@alumni.caltech.edu: [HACKERS... Tom Lane
- re: [lockhart@alumni.caltech.edu: [HAC... matthew green
- Re: [lockhart@alumni.caltech.edu:... Thomas Lockhart