X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 16886D1E0DD for ; Fri, 20 Feb 2004 16:37:19 +0000 (GMT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 31659-09 for ; Fri, 20 Feb 2004 12:37:14 -0400 (AST) Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by svr1.postgresql.org (Postfix) with ESMTP id 22096D1E0DE for ; Fri, 20 Feb 2004 12:37:14 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.12.11/8.12.11) with ESMTP id i1KGbDdA028460; Fri, 20 Feb 2004 11:37:13 -0500 (EST) To: Olivier Hubaut Cc: PgSQL SQL Subject: Re: Creating constraint sometime fail in a transaction In-reply-to: <40362CA5.2070007@scmbb.ulb.ac.be> References: <40362CA5.2070007@scmbb.ulb.ac.be> Comments: In-reply-to Olivier Hubaut message dated "Fri, 20 Feb 2004 16:49:57 +0100" Date: Fri, 20 Feb 2004 11:37:13 -0500 Message-ID: <28459.1077295033@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: by amavisd-new at postgresql.org X-Archive-Number: 200402/311 X-Sequence-Number: 17001 Olivier Hubaut writes: > So, we're wondering if the action for putting/removing constraint could > be executed out of the transaction, so that it may overlaps and crash in > such case. > Does anyone notice the same problem? When you didn't show us exactly what you're doing or exactly what went wrong, it's impossible to say ... regards, tom lane