Re: segv's on CREATE INDEX with recent HEAD... - Mailing list pgsql-bugs

From Sean Chittenden
Subject Re: segv's on CREATE INDEX with recent HEAD...
Date
Msg-id 20030529063433.GE62688@perrin.int.nxad.com
Whole thread Raw
In response to Re: segv's on CREATE INDEX with recent HEAD...  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: segv's on CREATE INDEX with recent HEAD...  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
> Sean Chittenden <sean@chittenden.org> writes:
> > PS What's the dilly with the server(s)?  I haven't gotten a commit
> >    message all day, but CVSup and anoncvs picked up the change.
>
> Well, the CVS master server has been pretty much 100% through this
> whole rigmarole (kudos to Marc for keeping up what *had* to be up ;-))
> The anoncvs mirror was busted for a couple days but has been okay since
> then, AFAIK.  The pgsql-committers list is still, uh, AWOL.  I get the
> impression that the listserv doesn't think the CVS server is authorized
> to send mail to the list, and that Marc has been manually approving
> batches of mail every couple days but hasn't got round to locating the
> real problem yet.  I trust he'll get it fixed before much longer though
> ...

Hardware problems are the worst.  Best of Marc.  Well, normally you're
good about committing things in batches, but I'm not sure if I'm
building against a complete/up to date version, but here is some
regression.diff fun to digest.  Looks like expected/misc.out and
./expected/sanity_check.out need to be updated and there's something
wrong with triggers/constraints:

*** ./expected/constraints.out  Wed May 28 23:26:42 2003
--- ./results/constraints.out   Wed May 28 23:28:15 2003
***************
*** 191,210 ****
  CREATE TABLE INSERT_CHILD (cx INT default 42,
        cy INT CHECK (cy > x))
        INHERITS (INSERT_TBL);
  INSERT INTO INSERT_CHILD(x,z,cy) VALUES (7,-7,11);
  INSERT INTO INSERT_CHILD(x,z,cy) VALUES (7,-7,6);
! ERROR:  ExecInsert: rejected due to CHECK constraint "insert_child_cy" on "insert_child"
  INSERT INTO INSERT_CHILD(x,z,cy) VALUES (6,-7,7);
! ERROR:  ExecInsert: rejected due to CHECK constraint "$1" on "insert_child"
  INSERT INTO INSERT_CHILD(x,y,z,cy) VALUES (6,'check failed',-6,7);
! ERROR:  ExecInsert: rejected due to CHECK constraint "insert_con" on "insert_child"
  SELECT * FROM INSERT_CHILD;
!  x |   y    | z  | cx | cy
! ---+--------+----+----+----
!  7 | -NULL- | -7 | 42 | 11
! (1 row)
!
  DROP TABLE INSERT_CHILD;
  --
  -- Check constraints on INSERT INTO
  --
--- 191,209 ----
  CREATE TABLE INSERT_CHILD (cx INT default 42,
        cy INT CHECK (cy > x))
        INHERITS (INSERT_TBL);
+ ERROR:  RelationClearRelation: relation 135137 deleted while still in use
  INSERT INTO INSERT_CHILD(x,z,cy) VALUES (7,-7,11);
+ ERROR:  Relation "insert_child" does not exist
  INSERT INTO INSERT_CHILD(x,z,cy) VALUES (7,-7,6);
! ERROR:  Relation "insert_child" does not exist
  INSERT INTO INSERT_CHILD(x,z,cy) VALUES (6,-7,7);
! ERROR:  Relation "insert_child" does not exist
  INSERT INTO INSERT_CHILD(x,y,z,cy) VALUES (6,'check failed',-6,7);
! ERROR:  Relation "insert_child" does not exist
  SELECT * FROM INSERT_CHILD;
! ERROR:  Relation "insert_child" does not exist
  DROP TABLE INSERT_CHILD;
+ ERROR:  table "insert_child" does not exist
  --
  -- Check constraints on INSERT INTO
  --

======================================================================

*** ./expected/triggers.out     Sat Nov 23 10:13:22 2002
--- ./results/triggers.out      Wed May 28 23:28:15 2003
***************
*** 87,92 ****
--- 87,93 ----
  NOTICE:  check_pkeys_fkey_cascade: 1 tuple(s) of fkeys are deleted
  NOTICE:  check_pkeys_fkey_cascade: 1 tuple(s) of fkeys2 are deleted
  DROP TABLE pkeys;
+ ERROR:  Relation 120339 does not exist
  DROP TABLE fkeys;
  DROP TABLE fkeys2;
  -- -- I've disabled the funny_dup17 test because the new semantics

======================================================================

*** ./expected/sanity_check.out Wed May 28 09:04:02 2003
--- ./results/sanity_check.out  Wed May 28 23:28:29 2003
***************
*** 58,68 ****
   pg_statistic        | t
   pg_trigger          | t
   pg_type             | t
   road                | t
   shighway            | t
   tenk1               | t
   tenk2               | t
! (52 rows)

  --
  -- another sanity check: every system catalog that has OIDs should have
--- 58,69 ----
   pg_statistic        | t
   pg_trigger          | t
   pg_type             | t
+  pkeys               | t
   road                | t
   shighway            | t
   tenk1               | t
   tenk2               | t
! (53 rows)

  --
  -- another sanity check: every system catalog that has OIDs should have

======================================================================

*** ./expected/misc.out Wed May 28 23:26:42 2003
--- ./results/misc.out  Wed May 28 23:28:39 2003
***************
*** 633,638 ****
--- 633,639 ----
   onek2
   path_tbl
   person
+  pkeys
   point_tbl
   polygon_tbl
   ramp
***************
*** 657,663 ****
   toyemp
   varchar_tbl
   xacttest
! (93 rows)

  --SELECT name(equipment(hobby_construct(text 'skywalking', text 'mer'))) AS equip_name;
  SELECT hobbies_by_name('basketball');
--- 658,664 ----
   toyemp
   varchar_tbl
   xacttest
! (94 rows)

  --SELECT name(equipment(hobby_construct(text 'skywalking', text 'mer'))) AS equip_name;
  SELECT hobbies_by_name('basketball');

======================================================================



Sorry for the bad news... or incomplete Sup.  This a local problem
(incomplete checkout?) or is there something else going on?  -sc

--
Sean Chittenden

pgsql-bugs by date:

Previous
From: Tom Lane
Date:
Subject: Re: segv's on CREATE INDEX with recent HEAD...
Next
From: Tom Lane
Date:
Subject: Re: segv's on CREATE INDEX with recent HEAD...