From: G. Anthony Reina <reina@nsi.edu>
To: pgsql-hackers@postgresql.org
Subject: Number of tuples (20300) not the same as heap (20301)
Date: Mon, 26 Apr 1999 18:18:12 -0700
Message-ID: <37251053.BF67F3C1@nsi.edu> (raw)
I have a table in which the first four variables are the unique primary
key. Recently, I ran a vacuum and was told that the number of tuples did
not equal the number in the heap for the primary key index to this
table. I'm not exactly sure whatn this means. It sounds like one or more
of the "unique" keys may have more than one set of data.
I often update the table using a text file containing the "UPDATE
table_name SET ..." and running the \i command in psql to execute the
commands from the text file. For some of these updates, I update an
variable length array that sometimes is longer than 8K. So what I do is
just update the first 100 or so positions in that array and get the
remaining positions with another update. I'm wondering if somehow there
is a bug that doesn't like this a ocassionally screws up the indexing.
Anyone know what this error means? I've tried dropping the index and
re-creating it but still get the same error on a vacuum.
Thanks.
-Tony
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 using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: reina@nsi.edu
Subject: Re: Number of tuples (20300) not the same as heap (20301)
In-Reply-To: <37251053.BF67F3C1@nsi.edu>
* 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