>> Currently, if you specify an index opclass then the system assumes that
>> you know what you are doing; there is no cross-check to see if the
>> chosen operators will work with the column datatype. That bothers me,
>> but I hesitate to insert a type-compatibility check; I wonder whether
>> the
Tom Lane wrote:
> Actually, I don't have to look very hard:
>
> CREATE TABLE td_products ( grp CHAR(2), cat CHAR(2), sub CHAR(2), vend_code
>CHAR(6), manu_part CHAR(20), part_num CHAR(15), descr CHAR(50), cost NUMERIC(10,2),
>retail NUMERIC(10,2), qty INT4, list_price NUMERIC(10,2), eff_
>> Wups, got it already. It happens on the second insert, luckily (the db is
>> HUGE :-). I've attached the offending SQL script.
> Got it, confirm seeing the crash here. I have to do real work now :-(
> but will look into it tonight.
Actually, I don't have to look very hard:
CREATE TABLE td
Frank Mayhar <[EMAIL PROTECTED]> writes:
> This probably depends heavily on the data I'm using and the script I
> wrote.
Yeah, probably so. Can you extract an SQL script that causes the
problem? That would make it possible to try to reproduce the failure
here, which would vastly simplify debugg
POSTGRESQL BUG REPORT TEMPLATE
Your name : Frank Mayhar
Your email address : [EMAIL PR
