Port Bug Report: Cannot insert more data into database

============================================================================
POSTGRESQL BUG REPORT TEMPLATE
============================================================================

Your name : Juha Virtanen
Your email address : jiivee(at)iki(dot)fi

Category : runtime: back-end
Severity : critical

Summary: Cannot insert more data into database

System Configuration
--------------------
Operating System : RedHat 5-2 Linux

PostgreSQL version : 6.3.2

Compiler used : gcc

Hardware:
---------
Linux xx.domain.fi 2.0.36 #5 Fri Mar 19 22:25:33 EET 1999 i586 unknown

memory 64 Mb, SCSI disks, plenty of disk space - no disk full condition.

Versions of other tools:
------------------------

--------------------------------------------------------------------------

Problem Description:
--------------------
Error message is:
COPY domains FROM '/tmp/domains_dbinsert.pl.4503' USING DELIMITERS '|';
Error Message: FATAL 1: btree: items are out of order (leftmost 0, stack 47, update 2)

After that, no more data can be inserted into database.

Database contains one table to which data is copied, copying inserts currently about 14000 records at a time.

domainsfi=> select count (*) from domains;
count
-------
1411027
(1 row)

domainsfi=> \d domains

Table = domains
+----------------------------------+----------------------------------+-------+
| Field | Type | Length|
+----------------------------------+----------------------------------+-------+
| domain | text | var || holder | text | var |
| date | date | 4 |
| time | time | 8 |
| haswww | int4 | 4 |
| webserver | text | var |
+----------------------------------+----------------------------------+-------+
domainsfi=>

--------------------------------------------------------------------------

Test Case:
----------
I guess it's not easy...

I did restore a correctly working database from backup and then insert the data not in it into database.

I did this twice and the showstopper bug showed up repeatedly.

I'm now heading towards 6.4.2 to see if it can hold 1.5 million records (and more) data.

--------------------------------------------------------------------------

Solution:
---------

--------------------------------------------------------------------------