On Fri, 6 Jun 1997, Vadim B. Mikheev wrote:
> Date: Fri, 06 Jun 1997 15:19:52 +0800
> From: "Vadim B. Mikheev" <vadim@sable.krasnoyarsk.su>
> To: Michael Reifenberger <root@totum.plaut.de>
> Cc: PostgreSQL Hackers <hackers@postgreSQL.org>, scrappy@hub.org
> Subject: Re: [HACKERS] FATAL 1:btree: items are out of order
>
> Well, I hope that bug reported by Michael is old bug.
>
...
> BTW, there shouldn't be problems in using btree for variable
> length attributes if there are no duplicates... Michael, are there
> duplicates in your table ?
>
Yes.
- -- Lets look for duplicates.
- -- And we have lots of them
SELECT count(*) FROM h;
...
(341224 rows)
SELECT DISTINCT firmennummer FROM h;
...
(111060 rows)
SELECT DISTINCT imp_exp_code FROM h;
...
(5 rows)
SELECT DISTINCT position FROM h;
...
(79 rows)
SELECT DISTINCT branchen FROM h;
...
(15200 rows)
- ---------------------------
If there is a bug regarding dublicates and btrees, why does work a:
CREATE TABLE ...
COPY ... FROM ...
CREATE INDEX ...
Does this bug occure only during inserts.
If the bug can't be fixed for 6.1 then he should be documented.
(Any chance to reproduce it in a regression test?)
Thanks anyway for responding.
Bye!
- ----
Michael Reifenberger
Plaut Software GmbH, R/3 Basis
PS: Do you still need my debugging-info you requested before?
------------------------------
