cvs tip problems - Mailing list pgsql-hackers

From Joe Conway
Subject cvs tip problems
Date
Msg-id 010601c14a21$e8357c00$0705a8c0@jecw2k1
Whole thread Raw
Responses Re: cvs tip problems
List pgsql-hackers
I just grabbed cvs tip this afternoon and ran into two issues:

- First one is that the regression fails on "geometry" on what appears to be
a difference in the 13th decimal place of the output value. See the attached
regression diff.
- Second was on reloading my data, I got the following error message (4
times):   ERROR:  operator class "timestamp_ops" does not accept data type
timestamp with time zone

I've not seen either of these problems before, and I've gone through this
routine at least a dozen times in the past month or so. The second problem
is caused by the following statements (auto generated by pg_dumpall):

CREATE UNIQUE INDEX "lda_idx_1" on "laser_diagnostic_activity" using btree
( "laser_sn" "varchar_ops", "diag_run_date" "timestamp_ops" );
CREATE  INDEX "ldi_idx_1" on "laser_diagnostic_items" using btree (
"laser_sn" "varchar_ops", "diag_run_date" "timestamp_ops", "diag_type"
"bpchar_ops", "diag_item" "int4_ops" );
CREATE  INDEX "lv_processed_hdr_idx4" on "lv_processed_hdr" using btree (
"lv_dt" "timestamp_ops" );
CREATE  INDEX "lv_processed_hdr_idx3" on "lv_processed_hdr" using btree (
"laser_type" "varchar_ops", "lv_dt" "timestamp_ops" );

And the related tables look like:

CREATE TABLE "laser_diagnostic_activity" (       "lda_id" integer DEFAULT
nextval('"laser_diagnostic_act_lda_id_seq"'::text) NOT NULL,       "laser_sn" character varying(15) NOT NULL,
"diag_run_date"timestamp with time zone NOT NULL,       "diag_ul_date" timestamp with time zone NOT NULL,
Constraint"laser_diagnostic_activity_pkey" Primary Key ("lda_id")
 
);

CREATE TABLE "laser_diagnostic_items" (       "ldi_id" integer DEFAULT
nextval('"laser_diagnostic_ite_ldi_id_seq"'::text) NOT NULL,       "laser_sn" character varying(15) NOT NULL,
"diag_run_date"timestamp with time zone NOT NULL,       "diag_type" character(1) NOT NULL,       "diag_item" integer
NOTNULL,       "diag_description" character varying(20) NOT NULL,       "diag_value" character varying(24),
"diag_units"character varying(10),       "lda_id" integer,       Constraint "laser_diagnostic_items_pkey" Primary Key
("ldi_id")
);

CREATE TABLE "lv_processed_hdr" (       "hdr_id" integer NOT NULL,       "laser_sn" character varying(15) NOT NULL,
 "config_id" integer,       "file_path" character varying(255) NOT NULL,       "file_name" character varying(255) NOT
NULL,      "lv_dt" timestamp with time zone NOT NULL,       "orig_lv_file" character varying(255) NOT NULL,
"app_ver"character varying(50) NOT NULL,       "lte_name" character varying(50) NOT NULL,       "lte_login" character
varying(50)NOT NULL,       "integrator" character varying(25) NOT NULL,       "laser_type" character varying(50) NOT
NULL,      "test_name" character varying(50) NOT NULL,       "data_set_name" character varying(50) NOT NULL,
"data_set_id"character varying(50) NOT NULL
 
);

Any suggestions?

Thanks,

Joe




pgsql-hackers by date:

Previous
From: "Marc G. Fournier"
Date:
Subject: Re: ftp.postgresql.org points to new server ...
Next
From: Bruce Momjian
Date:
Subject: Re: Pre-forking backend