X-Original-To: pgsql-sql-postgresql.org@localhost.postgresql.org
Received: from localhost (neptune.hub.org [200.46.204.2])
	by svr1.postgresql.org (Postfix) with ESMTP id 28F3AD1E241
	for <pgsql-sql-postgresql.org@localhost.postgresql.org>;
	Mon, 19 Jan 2004 06:20:48 +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 28822-06
	for <pgsql-sql-postgresql.org@localhost.postgresql.org>;
	Mon, 19 Jan 2004 02:20:17 -0400 (AST)
Received: from sss.pgh.pa.us (unknown [192.204.191.242])
	by svr1.postgresql.org (Postfix) with ESMTP id 03E79D1E810
	for <pgsql-sql@postgresql.org>; Mon, 19 Jan 2004 02:20:16 -0400 (AST)
Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1])
	by sss.pgh.pa.us (8.12.10/8.12.10) with ESMTP id i0J6K3pH021289;
	Mon, 19 Jan 2004 01:20:03 -0500 (EST)
To: sad <sad@bankir.ru>
Cc: pgsql-sql@postgresql.org
Subject: Re: DROP TRIGGER 
In-reply-to: <200401141445.27692.sad@bankir.ru> 
References: <200401141445.27692.sad@bankir.ru>
Comments: In-reply-to sad <sad@bankir.ru>
	message dated "Wed, 14 Jan 2004 14:45:27 +0000"
Date: Mon, 19 Jan 2004 01:20:03 -0500
Message-ID: <21288.1074493203@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
X-Virus-Scanned: by amavisd-new at postgresql.org
X-Archive-Number: 200401/164
X-Sequence-Number: 16557

sad <sad@bankir.ru> writes:
> ... now the database seems damaged in strange manner:
> Postgres cannot drop nor create some triggers 
> (he was thinking about an hour on the query then i have cancelled)

Could you try it again and get a stack trace to show exactly where it's
hung up?

			regards, tom lane