Re: [HACKERS] Btree or not btree? That is the question

2012-07-10 Thread Greg Sabino Mullane
On Mon, Jul 09, 2012 at 04:02:13PM -0400, Tom Lane wrote: ... Could you crank up the log verbosity so we can get file and line number, at least? Here is what the increased verbosity reveals in aggregate. This is about an 18-hour span, covering 12.5M transactions, on version 8.3.18: (13

Re: [HACKERS] Btree or not btree? That is the question

2012-07-09 Thread Greg Sabino Mullane
I've expanded my searching a bit, to see if I can find any other correlations. One thing that seems to happen about 10 times a day is an error of this sort: ERROR: could not open relation with OID 1554847326 In this case, the OID in question always exists, and corresponds to one of a handful

Re: [HACKERS] Btree or not btree? That is the question

2012-07-09 Thread Tom Lane
Greg Sabino Mullane g...@endpoint.com writes: I've expanded my searching a bit, to see if I can find any other correlations. One thing that seems to happen about 10 times a day is an error of this sort: ERROR: could not open relation with OID 1554847326 Is that the *entire* message? No

Re: [HACKERS] Btree or not btree? That is the question

2012-07-09 Thread Greg Sabino Mullane
ERROR: could not open relation with OID 1554847326 Is that the *entire* message? No details? Could you crank up the log verbosity so we can get file and line number, at least? Yes, that's the entire thing, other than the statement line after it. In this particular case: STATEMENT:

Re: [HACKERS] Btree or not btree? That is the question

2012-07-09 Thread Greg Sabino Mullane
Could you crank up the log verbosity so we can get file and line number, at least? First hit since the change: ERROR: XX000: could not open relation with OID 1554847444 LOCATION: relation_open, heapam.c:879 STATEMENT: SELECT ... Will leave the verbosity up and see if it occurs in the same

Re: [HACKERS] Btree or not btree? That is the question

2012-06-21 Thread Greg Sabino Mullane
ERROR: index pg_class_oid_index is not a btree That means you got bogus data while reading the metapage. I'm beginning to wonder about the hardware on this server ... This happened again, and this time I went back through the logs and found that it is always the exact same query causing

Re: [HACKERS] Btree or not btree? That is the question

2012-06-21 Thread Tom Lane
Greg Sabino Mullane g...@endpoint.com writes: ERROR: index pg_class_oid_index is not a btree That means you got bogus data while reading the metapage. I'm beginning to wonder about the hardware on this server ... This happened again, and this time I went back through the logs and found

Re: [HACKERS] Btree or not btree? That is the question

2012-06-21 Thread Greg Sabino Mullane
I dug through the logs and found some other occurances of the could not read block errors. Some on dirt simple SELECT queries. Nothing else has generated the btree error yet. About 35 found in the last month. This theory would be more plausible if you're wrong about the second-case tables

Re: [HACKERS] Btree or not btree? That is the question

2012-06-06 Thread Greg Sabino Mullane
On Mon, Jun 04, 2012 at 02:09:44PM -0400, Tom Lane wrote: Greg Sabino Mullane g...@endpoint.com writes: We have a 8.3.18 system (yes, the same one from the previous thread, finally upgraded!) that gave us this error yesterday: ERROR: index pg_class_oid_index is not a btree That means

Re: [HACKERS] Btree or not btree? That is the question

2012-06-04 Thread Tom Lane
Greg Sabino Mullane g...@endpoint.com writes: We have a 8.3.18 system (yes, the same one from the previous thread, finally upgraded!) that gave us this error yesterday: ERROR: index pg_class_oid_index is not a btree That means you got bogus data while reading the metapage. I'm beginning to