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

Peripheral Links

Header And Logo

PostgreSQL
| The world's most advanced open source database.

Site Navigation

Search for
  Advanced Search

Re: Cause of ERROR: could not open relation 1663/856689/856777: Invalid argument?



Wyatt --

We got a spate of similar errors recently; turned out to be a disk was not mounted properly. Once it was reseated all was well. You might also do a RAM check just to make sure that something isn't wonky there.

IIRC, I was told (see the archives of the postgres admin mail list) that this is an errant index, so you might try reindexing the table and see if you get the errors or if they go away.

HTH,

Greg WIlliamson
DBA
GlobeXplorer LLC

-----Original Message-----
From:	pgsql-general-owner(at)postgresql(dot)org on behalf of Wyatt Tellis
Sent:	Sat 9/30/2006 9:08 AM
To:	pgsql-general(at)postgresql(dot)org
Cc:	
Subject:	[GENERAL] Cause of ERROR: could not open relation 1663/856689/856777:  Invalid argument?

Hi,

I'm running 8.1.4 on W2K3 R2. I occasionally get errors of the type:

ERROR: could not open relation 1663/856689/856777: Invalid argument

where the last two numbers change. This only seems to happen during 
inserts into the largest table in the database (>500,000 rows). What 
does this error message mean?


Thanks.



---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster


-------------------------------------------------------
Click link below if it is SPAM gsw(at)globexplorer(dot)com
"https://mailscanner.globexplorer.com/dspam/dspam.cgi?signatureID=451e9d02292579835456387&user=gsw(at)globexplorer(dot)com&retrain=spam&template=history&history_page=1"
!DSPAM:451e9d02292579835456387!
-------------------------------------------------------








Home | Main Index | Thread Index

Privacy Policy | PostgreSQL Archives hosted by Command Prompt, Inc. | Designed by tinysofa
Copyright © 1996 – 2008 PostgreSQL Global Development Group