share|improve this answer answered May 15 '13 at 1:10 Chris Travers 12.8k424107 add a comment| Your Answer draft saved draft discarded Sign up or log in Sign up using Google Haveyoutried running any hardware diagnostics? Rodrigo Gonzalez at Jun 26, 2008 at 6:35 am ⇧ Tom Lane wrote:Rodrigo Gonzalez
Which one? How is the Heartbleed exploit even possible? looking again at your latest problem query, the query is buggy:db=# SELECT ... Also pg_dump cannot dump the DB.PgSQL version is 8.3.3 and happened one day after loading the DB there.Anything that can be done? have a peek here
This happened amidst a script doing inserts! I'm assuming you upgraded using dump/restore, orpostgres would have complained about the version of the data files atstartup, but maybe you did something unusual.Are you sure there's only one version of Is there a possibility that file system errors can bereported if there is a heavy load on the file system? In 8.3, 2836 is pg_proc's TOASTtable and should certainly never get deleted.
So cannot reproduce right now. You'd be better off using pg_relation_size(c.oid) anyway. If so, do you perhaps usemalloc/free instead of the ones Postgres provides (reasoning you maybe freeing a reference to the toast table somehow)?Is that data-file on a mirror where one part Do you have any stored Alban Hertroys at Jun 26, 2008 at 5:14 pm ⇧ On Jun 26, 2008, at 5:41 AM, Rodrigo Gonzalez wrote:Tom Lane wrote:Rodrigo Gonzalez
Error: Could not open relation with OID 54019. There was also two entries in pg_index forindex pg_class_oid_index. Still, you might have an issue with trying to use hardwarethat's not supported by RHEL4, especially if it's not a very recentversion of RHEL4. https://www.postgresql.org/message-id/[email protected] Everythingwent ok, no errors or anything, but when I checked pg_tables -view I saw twotables with the same name.
With a RAID of 8x750GB disks, it will take a *long* time to check, if you cannot simply replace all disks at once. I've tried to figure out the OIDs and connections between all the tables involved, to figure out where that reference to non-existent OID is, but i have failed. Posted on 2008-02-27 06:19:38 by Tom Lane Darren Reed
delete from pg_rewrite where oid = 16403;
And see if this can fix the problem..
Fujitsu Australia Software Technology
shoaibm[@]fast.fujitsu.com.au ------=_Part_4587_22010139.1204007588015-- Report this message #3: Re:
Please help us. Any log you need or want? Error Message From Server Error Could Not Open Relation No stored procedure in C, just SQL and PlPgSQL store procedures are used. I also haveother db clusters running on different filesystems (also gfs) and I havenever had any problems with them.RegardsMikko reply | permalink Tom Lane Some RAM checks wouldn't be out of
Darren ---------------------------(end of broadcast)--------------------------- TIP 3: Have you checked our extensive FAQ? Memtest showed no problems, and everything looks fine. Regards Mikko Mikko Partio at Apr 17, 2008 at 4:09 pm ⇧ On Thu, Apr 17, 2008 at 7:06 PM, Tom Lane wrote:"Mikko Partio"
We stilldon't know what the original problem was, but I wonder if it might havebeen of the same ilk. You can determine which table it is: 1) get database name: select * from pg_database where oid=17369 2) get table name (connect to affected database): select * from pg_class where oid=1684 How? Please reindex you database and then try inserting the data in the table.
WARNING: index "ip_dst_idx" contains Lennin Caro at Jun 27, 2008 at 2:43 pm ⇧ use REINDEXhttp://www.postgresql.org/docs/8.3/static/sql-reindex.htmltell us the resultthank--- On Fri, 6/27/08, Ganbold wrote:From: Ganbold
asked 3 years ago viewed 4515 times active 3 months ago Related 903PostgreSQL “DESCRIBE TABLE”0Npgsql & Postgresql : ERROR: XX001: could not read block 2354 of relation632Show tables in PostgreSQL382Insert, on
A CLUSTER operation was done on a table succesfully, afterwards when trying to access the table I get the error 2008-04-17 13:05:30 EEST : [32-1] ERROR: could not open relation 1663/16386/359232: Maybe something wentwrong there? Create table script is: create table COMPANY( companyId bigint NOT NULL, name varchar(255) NULL, PRIMARY KEY(companyId) ); Sequence used is: "CREATE SEQUENCE COMPANY_SEQ MINVALUE 1 MAXVALUE 9223372036854775807 INCREMENT BY 1 START Is there any other method fixing the index?thanks in advance,Ganbold--Sent via pgsql-general mailing list ([email protected])To make changes to your subscription:http://www.postgresql.org/mailpref/pgsql-general reply | permalink Ganbold It shows following when I try to
Have youtried running any hardware diagnostics? Thanks for your time and if I see the error again I will write again. Version?Otherwise:- What OS and version are you using?- What filesystem type is the database on?- Are you using any sort of RAID / LVM? more stack exchange communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed
The cause can be a cached plan. Version 8.2 on windows.I think I had an hardware issue in the past where my box rebooted fewtimes I assume this is due to that thing.I tried to re index them Only restore from backup. Everythingwent ok, no errors or anything, but when I checked pg_tables -view I saw twotables with the same name.
After that I tried to remove indexes from the table in question: # drop index xxx_idx; ERROR: could not read block 0 of relation 1663/16386/2673: read only 0 of 8192 bytes DId you try REINDEX on the table ?