Le jeudi 14 janvier 2010 17:17:47, Dan Langille a écrit : > Are these new regression testing errors to be expected? Are they > permanent or just for short term testing..
No, they should disappear. I will look and fix the problem. Bye > If permanent, I will add filtering to ignore them. Otherwise, I will > wait until they go away. > > > Jan 14 16:00:24 dbclone postgres[5806]: [2-1] ERROR: relation > > "pathhierarchy" already exists Jan 14 16:00:24 dbclone postgres[5806]: > > [3-1] ERROR: relation "pathhierarchy_ppathid" already exists Jan 14 > > 16:00:24 dbclone postgres[5806]: [4-1] ERROR: relation "pathvisibility" > > already exists Jan 14 16:00:24 dbclone postgres[5806]: [5-1] ERROR: > > relation "pathvisibility_jobid" already exists Jan 14 16:01:10 dbclone > > postgres[6105]: [2-1] ERROR: relation "pathhierarchy" already exists Jan > > 14 16:01:10 dbclone postgres[6105]: [3-1] ERROR: relation > > "pathhierarchy_ppathid" already exists Jan 14 16:01:10 dbclone > > postgres[6105]: [4-1] ERROR: relation "pathvisibility" already exists > > Jan 14 16:01:10 dbclone postgres[6105]: [5-1] ERROR: relation > > "pathvisibility_jobid" already exists > > > > > > Jan 14 16:00:24 dbclone postgres[5806]: [2-2] STATEMENT: CREATE TABLE > > PathHierarchy Jan 14 16:00:24 dbclone postgres[5806]: [2-3] ( > > Jan 14 16:00:24 dbclone postgres[5806]: [2-4] PathId integer NOT > > NULL, Jan 14 16:00:24 dbclone postgres[5806]: [2-5] PPathId > > integer > > NOT NULL, Jan 14 16:00:24 dbclone postgres[5806]: [2-6] CONSTRAINT > > pathhierarchy_pkey PRIMARY KEY (PathId) Jan 14 16:00:24 dbclone > > postgres[5806]: [2-7] ); > > Jan 14 16:00:24 dbclone postgres[5806]: [3-2] STATEMENT: CREATE INDEX > > pathhierarchy_ppathid Jan 14 16:00:24 dbclone postgres[5806]: [3-3] > > > > ON PathHierarchy (PPathId); Jan 14 16:00:24 dbclone postgres[5806]: > > [4-2] STATEMENT: CREATE TABLE PathVisibility Jan 14 16:00:24 dbclone > > postgres[5806]: [4-3] ( > > Jan 14 16:00:24 dbclone postgres[5806]: [4-4] PathId integer NOT > > NULL, Jan 14 16:00:24 dbclone postgres[5806]: [4-5] JobId > > integer > > NOT NULL, Jan 14 16:00:24 dbclone postgres[5806]: [4-6] Size int8 > > DEFAULT 0, Jan 14 16:00:24 dbclone postgres[5806]: [4-7] Files > > int4 DEFAULT 0, Jan 14 16:00:24 dbclone postgres[5806]: [4-8] > > CONSTRAINT pathvisibility_pkey PRIMARY KEY (JobId, PathId) Jan 14 > > 16:00:24 dbclone postgres[5806]: [4-9] ); > > Jan 14 16:00:24 dbclone postgres[5806]: [5-2] STATEMENT: CREATE INDEX > > pathvisibility_jobid Jan 14 16:00:24 dbclone postgres[5806]: [5-3] > > ON PathVisibility (JobId); Jan 14 16:01:10 dbclone postgres[6105]: > > [2-2] STATEMENT: CREATE TABLE PathHierarchy Jan 14 16:01:10 dbclone > > postgres[6105]: [2-3] ( > > Jan 14 16:01:10 dbclone postgres[6105]: [2-4] PathId integer NOT > > NULL, Jan 14 16:01:10 dbclone postgres[6105]: [2-5] PPathId > > integer > > NOT NULL, Jan 14 16:01:10 dbclone postgres[6105]: [2-6] CONSTRAINT > > pathhierarchy_pkey PRIMARY KEY (PathId) Jan 14 16:01:10 dbclone > > postgres[6105]: [2-7] ); > > Jan 14 16:01:10 dbclone postgres[6105]: [3-2] STATEMENT: CREATE INDEX > > pathhierarchy_ppathid Jan 14 16:01:10 dbclone postgres[6105]: [3-3] > > > > ON PathHierarchy (PPathId); Jan 14 16:01:10 dbclone postgres[6105]: > > [4-2] STATEMENT: CREATE TABLE PathVisibility Jan 14 16:01:10 dbclone > > postgres[6105]: [4-3] ( > > Jan 14 16:01:10 dbclone postgres[6105]: [4-4] PathId integer NOT > > NULL, Jan 14 16:01:10 dbclone postgres[6105]: [4-5] JobId > > integer > > NOT NULL, Jan 14 16:01:10 dbclone postgres[6105]: [4-6] Size int8 > > DEFAULT 0, Jan 14 16:01:10 dbclone postgres[6105]: [4-7] Files > > int4 DEFAULT 0, Jan 14 16:01:10 dbclone postgres[6105]: [4-8] > > CONSTRAINT pathvisibility_pkey PRIMARY KEY (JobId, PathId) Jan 14 > > 16:01:10 dbclone postgres[6105]: [4-9] ); > > Jan 14 16:01:10 dbclone postgres[6105]: [5-2] STATEMENT: CREATE INDEX > > pathvisibility_jobid Jan 14 16:01:10 dbclone postgres[6105]: [5-3] > > ON PathVisibility (JobId); ------------------------------------------------------------------------------ Throughout its 18-year history, RSA Conference consistently attracts the world's best and brightest in the field, creating opportunities for Conference attendees to learn about information security's most important issues through interactions with peers, luminaries and emerging and established companies. http://p.sf.net/sfu/rsaconf-dev2dev _______________________________________________ Bacula-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-devel
