Re: should I worry?

From: ohp(at)pyrenet(dot)fr
To: Heikki Linnakangas <heikki(at)enterprisedb(dot)com>
Cc: pgsql-hackers list <pgsql-hackers(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: should I worry?
Date: 2007-11-03 17:24:06
Message-ID: Pine.UW2.4.53.0711031820560.21951@sun.pyrenet
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Sorry to post on my own post,
I found this (as a little exemple I've got plenty of these)
could that be the culprit and how to correct that?
--
-- Name: RI_ConstraintTrigger_609094000; Type: TRIGGER; Schema: public; Owner: delain
--

CREATE CONSTRAINT TRIGGER "<unnamed>"
AFTER DELETE ON objets
FROM objet_position
NOT DEFERRABLE INITIALLY IMMEDIATE
FOR EACH ROW
EXECUTE PROCEDURE "RI_FKey_noaction_del"('<unnamed>', 'objet_position', 'objets', 'UNSPECIFIED', 'pobj_obj_cod', 'obj_cod');

--
-- Name: RI_ConstraintTrigger_609094001; Type: TRIGGER; Schema: public; Owner: delain
--

CREATE CONSTRAINT TRIGGER "<unnamed>"
AFTER UPDATE ON objets
FROM objet_position
NOT DEFERRABLE INITIALLY IMMEDIATE
FOR EACH ROW
EXECUTE PROCEDURE "RI_FKey_noaction_upd"('<unnamed>', 'objet_position', 'objets', 'UNSPECIFIED', 'pobj_obj_cod', 'obj_cod');

This dump was generated by pg_dump 8.3beta1 against a 8.2.5 db

Best regardsb
On Fri, 2 Nov 2007, Heikki Linnakangas wrote:

> Date: Fri, 02 Nov 2007 19:59:03 +0000
> From: Heikki Linnakangas <heikki(at)enterprisedb(dot)com>
> To: ohp(at)pyrenet(dot)fr
> Cc: pgsql-hackers list <pgsql-hackers(at)postgresql(dot)org>
> Subject: Re: [HACKERS] should I worry?
>
> ohp(at)pyrenet(dot)fr wrote:
> > On Fri, 2 Nov 2007, Heikki Linnakangas wrote:
> >
> >> Date: Fri, 02 Nov 2007 18:11:14 +0000
> >> From: Heikki Linnakangas <heikki(at)enterprisedb(dot)com>
> >> To: ohp(at)pyrenet(dot)fr
> >> Cc: pgsql-hackers list <pgsql-hackers(at)postgresql(dot)org>
> >> Subject: Re: [HACKERS] should I worry?
> >>
> >> ohp(at)pyrenet(dot)fr wrote:
> >>> I'm now testing 8.3beta2 on a relatively big (10G) database.
> >>> I've tried with pg_dymp -Fc/pg_restore and pg_dump/pgsql and get those
> >>> errors:
> >> Could you be a bit more specific? The database you tried to restore to
> >> was empty, right? Can you post the dump file (schema-only)?
> > Yes it was empty, Sorry, I can't post the schema, it belongs to one of my
> > customer...
>
> Maybe you could reduce it to a small self-contained test case, with
> table names changed to protect the innocent?
>
>

--
Olivier PRENANT Tel: +33-5-61-50-97-00 (Work)
15, Chemin des Monges +33-5-61-50-97-01 (Fax)
31190 AUTERIVE +33-6-07-63-80-64 (GSM)
FRANCE Email: ohp(at)pyrenet(dot)fr
------------------------------------------------------------------------------
Make your life a dream, make your dream a reality. (St Exupery)

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2007-11-03 17:27:22 Re: building 8.3beta2 w/ 'make check' consumes A LOT of disk space
Previous Message Tom Lane 2007-11-03 16:42:24 Re: should I worry?