Re: Server v7.3RC2 Dies - Mailing list pgsql-general

I have done
reindex table <the tables>
but still can not COPY. I have tried COPYing 4 or 5 different tables
without success. I guess my database is corrupted if no one else
encounters this same problem. If so, please ignore this problem as I can
rebuild the database though it takes much time.

> > This is to follow up my previous post.
> > I notice it is a problem coming from COPY command. I can select the table
> > but both COPY and pg_dump abort with similar messages.
>
> Bizarre.  What exactly is the schema of the table (pg_dump -s -t table2
> would be useful to see)?

--
-- PostgreSQL database dump
--

\connect - dba

SET search_path = public, pg_catalog;

--
-- TOC entry 2 (OID 17891)
-- Name: t1; Type: TABLE; Schema: public; Owner: dba
--

CREATE TABLE t1 (
    f1 integer DEFAULT nextval('"t1_f1_seq"'::text) NOT NULL
);


--
-- TOC entry 3 (OID 17894)
-- Name: t1_pkey; Type: CONSTRAINT; Schema: public; Owner: dba
--
ALTER TABLE ONLY t1
    ADD CONSTRAINT t1_pkey PRIMARY KEY (f1);

--
-- TOC entry 4 (OID 73547)
-- Name: RI_ConstraintTrigger_73547; Type: TRIGGER; Schema: public;
Owner: dba
--

CREATE CONSTRAINT TRIGGER fkd1f1
    AFTER DELETE ON t1
    FROM d1
    NOT DEFERRABLE INITIALLY IMMEDIATE
    FOR EACH ROW
    EXECUTE PROCEDURE "RI_FKey_cascade_del" ('fkd1f1', 'd1', 't1',
    'UNSPECIFIED', 'f1', 'f1');
-- TOC entry 5 (OID 73548)
-- Name: RI_ConstraintTrigger_73548; Type: TRIGGER; Schema: public;
Owner: dba
--

CREATE CONSTRAINT TRIGGER fkd1f1
    AFTER UPDATE ON t1
    FROM d1
    NOT DEFERRABLE INITIALLY IMMEDIATE
    FOR EACH ROW
    EXECUTE PROCEDURE "RI_FKey_cascade_upd" ('fkd1f1', 'd1', 't1',
    'UNSPECIFIED'
, 'f1', 'f1');

--
-- TOC entry 6 (OID 73556)
-- Name: RI_ConstraintTrigger_73556; Type: TRIGGER; Schema: public;
Owner: dba
--
CREATE CONSTRAINT TRIGGER fkt5f2
    AFTER DELETE ON t1
    FROM t5
    NOT DEFERRABLE INITIALLY IMMEDIATE
    FOR EACH ROW
    EXECUTE PROCEDURE "RI_FKey_noaction_del" ('fkt5f2', 't5', 't1',
    'UNSPECIFIED
', 'f2', 'f1');

--
-- TOC entry 7 (OID 73557)
-- Name: RI_ConstraintTrigger_73557; Type: TRIGGER; Schema: public;
Owner: dba
--

CREATE CONSTRAINT TRIGGER fkt5f2
    AFTER UPDATE ON t1
    FROM t5
    NOT DEFERRABLE INITIALLY IMMEDIATE
    FOR EACH ROW
    EXECUTE PROCEDURE "RI_FKey_noaction_upd" ('fkt5f2', 't5', 't1',
    'UNSPECIFIED', 'f2','f1');

> What shows up in the postmaster log?

How magic postgreSQL is! The log looks like postmaster is able to be
reborn by itself.

LOG:  database system was shut down at 2002-11-28 21:32:46 CST
LOG:  checkpoint record is at 0/20CBE0C
LOG:  redo record is at 0/20CBE0C; undo record is at 0/0; shutdown TRUE
LOG:  next transaction id: 5406; next oid: 98763
LOG:  database system is ready
LOG:  server process (pid 1625) was terminated by signal 11
LOG:  terminating any other active server processes
LOG:  all server processes terminated; reinitializing shared memory and
semaphores
LOG:  database system was interrupted at 2002-11-28 21:33:04 CST
LOG:  checkpoint record is at 0/20CBE0C
LOG:  redo record is at 0/20CBE0C; undo record is at 0/0; shutdown TRUE
LOG:  next transaction id: 5406; next oid: 98763
LOG:  database system was not properly shut down; automatic recovery in
progress
FATAL:  The database system is starting up
LOG:  ReadRecord: record with zero length at 0/20CBE4C
LOG:  redo is not required
LOG:  database system is ready

> Can you get a stack backtrace from the core dump?
>

I don't know how to do that! ^.^

Best regards,

CN
--
http://fastmail.fm - Same, same, but different...