Thread: LargeObjectDrop and simple_heap_delete - Are these errors normal?
Greetings! I'm a dba new to postgresql and I wanted to learn about these two error messages. I am getting these errors quite often and I'm wondering what it might be that is causing them. Could it be bad indexes? ...I've opened the database up in single user mode, and ran a 'reindex database databasename' successfully. Does anyoen have any hints or suggestions for me to try? I would not guess that these types of messages are 'normal', but I have no clue how to get rid of them. THANKS so much for your time and help, -techie@1stcounsel.com <Snippet from logfile - 6 minutes worth > [root@adsdb root]# tail -f /var/log/clus.ads.log 2003-07-30 10:08:50 ERROR: LargeObjectDrop: large object 4280306 not found 2003-07-30 10:08:58 LOG: recycled transaction log file 000000050000005B 2003-07-30 10:09:24 ERROR: LargeObjectDrop: large object 4280320 not found 2003-07-30 10:09:24 ERROR: LargeObjectDrop: large object 4280320 not found 2003-07-30 10:09:48 ERROR: LargeObjectDrop: large object 4280331 not found 2003-07-30 10:09:48 ERROR: LargeObjectDrop: large object 4280331 not found 2003-07-30 10:09:51 ERROR: simple_heap_delete: tuple concurrently updated 2003-07-30 10:09:57 ERROR: LargeObjectDrop: large object 4280354 not found 2003-07-30 10:09:58 ERROR: LargeObjectDrop: large object 4280365 not found 2003-07-30 10:09:58 ERROR: LargeObjectDrop: large object 4280365 not found 2003-07-30 10:10:36 ERROR: simple_heap_delete: tuple concurrently updated 2003-07-30 10:10:37 ERROR: LargeObjectDrop: large object 4280373 not found 2003-07-30 10:10:37 ERROR: LargeObjectDrop: large object 4280373 not found 2003-07-30 10:10:37 ERROR: LargeObjectDrop: large object 4280373 not found 2003-07-30 10:10:38 ERROR: simple_heap_delete: tuple concurrently updated 2003-07-30 10:10:38 ERROR: LargeObjectDrop: large object 4280388 not found 2003-07-30 10:10:42 ERROR: LargeObjectDrop: large object 4280393 not found 2003-07-30 10:10:42 ERROR: LargeObjectDrop: large object 4280393 not found 2003-07-30 10:11:07 ERROR: LargeObjectDrop: large object 4280397 not found 2003-07-30 10:11:22 ERROR: LargeObjectDrop: large object 4280412 not found 2003-07-30 10:11:22 ERROR: LargeObjectDrop: large object 4280412 not found 2003-07-30 10:12:04 ERROR: LargeObjectDrop: large object 4280415 not found 2003-07-30 10:12:06 ERROR: LargeObjectDrop: large object 4280440 not found 2003-07-30 10:12:06 ERROR: LargeObjectDrop: large object 4280440 not found 2003-07-30 10:12:06 ERROR: LargeObjectDrop: large object 4280442 not found 2003-07-30 10:12:06 ERROR: LargeObjectDrop: large object 4280442 not found 2003-07-30 10:12:06 ERROR: LargeObjectDrop: large object 4280442 not found 2003-07-30 10:12:52 ERROR: LargeObjectDrop: large object 4280449 not found 2003-07-30 10:12:52 ERROR: LargeObjectDrop: large object 4280449 not found 2003-07-30 10:12:55 ERROR: LargeObjectDrop: large object 4280478 not found 2003-07-30 10:12:55 ERROR: LargeObjectDrop: large object 4280478 not found 2003-07-30 10:12:55 ERROR: LargeObjectDrop: large object 4280478 not found 2003-07-30 10:13:00 ERROR: LargeObjectDrop: large object 4280482 not found 2003-07-30 10:13:06 ERROR: LargeObjectDrop: large object 4280472 not found 2003-07-30 10:13:49 ERROR: LargeObjectDrop: large object 4280525 not found 2003-07-30 10:13:49 ERROR: simple_heap_delete: tuple concurrently updated 2003-07-30 10:13:49 ERROR: simple_heap_delete: tuple concurrently updated 2003-07-30 10:13:57 ERROR: LargeObjectDrop: large object 4280531 not found 2003-07-30 10:13:57 ERROR: LargeObjectDrop: large object 4280531 not found 2003-07-30 10:13:57 ERROR: LargeObjectDrop: large object 4280531 not found 2003-07-30 10:14:04 ERROR: LargeObjectDrop: large object 4280521 not found 2003-07-30 10:14:05 LOG: recycled transaction log file 000000050000005C 2003-07-30 10:14:05 LOG: recycled transaction log file 000000050000005D 2003-07-30 10:14:36 ERROR: simple_heap_delete: tuple concurrently updated 2003-07-30 10:14:36 ERROR: simple_heap_delete: tuple concurrently updated 2003-07-30 10:14:38 ERROR: LargeObjectDrop: large object 4280567 not found 2003-07-30 10:14:38 ERROR: LargeObjectDrop: large object 4280567 not found 2003-07-30 10:14:38 ERROR: LargeObjectDrop: large object 4280567 not found 2003-07-30 10:14:39 ERROR: simple_heap_delete: tuple concurrently updated 2003-07-30 10:14:40 ERROR: simple_heap_delete: tuple concurrently updated Sent by 1stcounsel.com Mail Premium Accounts for Legal Professionals http://1stcounsel.com/
More information:
I'm running PostgreSQL version 7.3.2
on linux RH 8.0 (Linux version 2.4.18-14smp
(bhcompile@stripples.devel.redhat.com) (gcc
version 3.2 20020903 (Red Hat Linux 8.0 3.2-7))
After the most recent 'crash' I went into
single user mode, and did the following:
1) reindex database dbname --> 5 minutes to run
2) vacuum full ----> 45 minutes with the
following errors:
backend> vacuum full;
WARNING: Index
pg_attribute_relid_attnam_index: NUMBER OF
INDEX' TUPLES (1191) IS NOT THE SAME AS HEAP'
(1302).
Recreate the index.
WARNING: Index
pg_attribute_relid_attnum_index: NUMBER OF
INDEX' TUPLES (1191) IS NOT THE SAME AS HEAP'
(1302).
Recreate the index.
WARNING: Index pg_class_oid_index: NUMBER OF
INDEX' TUPLES (144) IS NOT THE SAME AS HEAP'
(180).
Recreate the index.
WARNING: Index pg_class_relname_nsp_index:
NUMBER OF INDEX' TUPLES (144) IS NOT THE SAME
AS HEAP' (180).
Recreate the index.
WARNING: Rel pg_largeobject: Uninitialized
page 399948 - fixing
WARNING: Index pg_largeobject_loid_pn_index:
NUMBER OF INDEX' TUPLES (227408) IS NOT THE
SAME AS HEAP' (1147110).
Recreate the index.
WARNING: Index pg_attrdef_adrelid_adnum_index:
NUMBER OF INDEX' TUPLES (145) IS NOT THE SAME
AS HEAP' (147).
Recreate the index.
WARNING: Index pg_attrdef_oid_index: NUMBER OF
INDEX' TUPLES (145) IS NOT THE SAME AS HEAP'
(147).
Recreate the index.
WARNING: Index pg_statistic_relid_att_index:
NUMBER OF INDEX' TUPLES (19) IS NOT THE SAME AS
HEAP' (324).
Recreate the index.
WARNING: Index pg_toast_16408_index: NUMBER OF
INDEX' TUPLES (0) IS NOT THE SAME AS HEAP' (3).
Recreate the index.
3) I then recreated the offending indexes like
the backend asked me to (except the backend
complained on the last one, where the number of
tuples was zero, claiming that the index did
not exist).
4) reindex database dbname --> 45 seconds to
run
stoped the backend, and let my customers back
in.
The LargeObjectDrop errors are still there, and
If I have a corrupted database I'ld love to do
WHATEVER it takes to fix it and ensure it
doesn't happen again. What did I do wrong?
THANKS AGAIN in advance,
techie@1stcounsel.com
Sent by 1stcounsel.com Mail
Premium Accounts for Legal Professionals
http://1stcounsel.com/
"tech techie" <techie@1stcounsel.com> writes:
> After the most recent 'crash' I went into
> single user mode, and did the following:
> 1) reindex database dbname --> 5 minutes to run
> 2) vacuum full ----> 45 minutes with the
> following errors:
> backend> vacuum full;
> WARNING: Index
> pg_attribute_relid_attnam_index: NUMBER OF
> INDEX' TUPLES (1191) IS NOT THE SAME AS HEAP'
> (1302).
> Recreate the index.
> [ etc ]
Whoa. If you are seeing that immediately after a reindex, then there's
something really wrong. Have you done any hardware diagnostics
recently? memtest86 and badblocks seem to be the standard tools to try.
regards, tom lane