From: Chris White (cjwhite) <cjwhite@cisco.com>
To: pgsql-admin@postgresql.org
Subject: Error seen when vacuuming pg_largeobject table
Date: Mon, 26 Jan 2004 17:11:45 -0800
Message-ID: <002001c3e472$88698fd0$24976b80@amer.cisco.com> (raw)
Following a power fail restart, when I vacuum the pg_largeobject table I
see the following error messages:
VACUUM: DEBUG sql sql sql DEBUG: --Relation pg_largeobject-- blocks 450
VACUUM: DEBUG sql sql sql DEBUG: Pages 450: Changed 78, reaped 277,
Empty 0, New 37; Tup 1390: Vac 232, Keep/VTL 0/0, UnUsed 220, MinLen 98,
MaxLen 2092; Re-using: Free/Avail. Space 1464136/1463348;
EndEmpty/Avail. Pages 0/445.
VACUUM: CPU 0.05s/0.01u sec elapsed 0.56 sec.
VACUUM: DEBUG sql sql sql DEBUG: Index pg_largeobject_loid_pn_index:
Pages 14; Tuples 1044: Deleted 232.
VACUUM: CPU 0.00s/0.00u sec elapsed 0.00 sec. VACUUM: INFO sql sql sql
NOTICE: Index pg_largeobject_loid_pn_index: NUMBER OF INDEX' TUPLES
(1044) IS NOT THE SAME AS HEAP' (1390).
VACUUM: Recreate the index.
VACUUM: WARNING sql sql sql ERROR: Cannot insert a duplicate key into
unique index pg_largeobject_loid_pn_index
When I run postgres with the -P and -O options to reindex the index,
everything seem to run okay, I see no error messages. However, when I
restart postmaster and try and do a vacuum again, I get the same error
messages.
What can I do to correct the problem?
Thanks
Chris White
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: cjwhite@cisco.com
Subject: Re: Error seen when vacuuming pg_largeobject table
In-Reply-To: <002001c3e472$88698fd0$24976b80@amer.cisco.com>
References: <002001c3e472$88698fd0$24976b80@amer.cisco.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox