Received: from localhost (unknown [200.46.204.183]) by developer.postgresql.org (Postfix) with ESMTP id DD1422E008E for ; Thu, 24 Apr 2008 06:57:28 -0300 (ADT) Received: from developer.postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 64023-06 for ; Thu, 24 Apr 2008 06:57:24 -0300 (ADT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by developer.postgresql.org (Postfix) with ESMTP id 4A92B2E0087 for ; Thu, 24 Apr 2008 06:57:24 -0300 (ADT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.14.1/8.14.1) with ESMTP id m3O9vJkp093204 for ; Thu, 24 Apr 2008 06:57:19 -0300 (ADT) (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.14.1/8.14.1/Submit) id m3O9Ujvo087081 for pgsql-admin@postgresql.org; Thu, 24 Apr 2008 06:30:45 -0300 (ADT) (envelope-from news) From: "Sabin Coanda" X-Newsgroups: pgsql.admin Subject: Re: loosing constraint at backup Date: Thu, 24 Apr 2008 12:30:53 +0300 Organization: Hub.Org Networking Services Lines: 6 Message-ID: References: X-Complaints-To: usenet@news.hub.org X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.3138 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3198 X-RFC2646: Format=Flowed; Response To: pgsql-admin@postgresql.org X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200804/244 X-Sequence-Number: 29008 After retrying the scenario, I found the problem is in the dump, and the constraint is missing in the backup file. Sabin