Bug? Insert into new Datatype 7.0.x

From: "Michael Miyabara-McCaskey" <mykarz(at)miyabara(dot)com>
To: <pgsql-general(at)postgresql(dot)org>
Subject: Bug? Insert into new Datatype 7.0.x
Date: 2000-12-07 20:15:18
Message-ID: 007c01c0608a$6b6f1810$aa00a8c0@ncc1701e
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Hello all,

I have been experiencing a strange problem.

I did a import into "table1", and for the sake of not having complaints, all
fields are set to "text". I then created a "table2" again with all types
set to text, and inserted a distinct set of the records from table1 into
table2. No problems.

However, when I created "table3" which I used the correct data types (oid,
float4, float4), and selected the 3 specific rows from table2, and inserted
them into table3... The query ran for a little while, and then the backend
crashes...

I fumbled around for a while, but finally recreated table3 as (oid, text,
text), and it worked fine... My question what caused the backend to crash?

The data I was inserting into table3, was the actual oid from table2, column
2 and column 3 were number values of the form "x.xxx", or a null value.

Any thoughts?

-Michael Miyabara-McCaskey

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Nathan Myers 2000-12-07 20:25:41 Re: CRCs (was: beta testing version)
Previous Message Soma Interesting 2000-12-07 20:00:05 multi-byte support