Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id ACA1D47708D for ; Thu, 11 Apr 2002 10:52:28 -0400 (EDT) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id g3BEqUF01057; Thu, 11 Apr 2002 10:52:30 -0400 (EDT) To: cnliou@eurosport.com Cc: pgsql-sql@postgresql.org Subject: Re: Problem With A Rule In-reply-to: <200204111109.12ab@th00.opsion.fr> References: <200204111109.12ab@th00.opsion.fr> Comments: In-reply-to message dated "Thu, 11 Apr 2002 11:09:18 +0000" Date: Thu, 11 Apr 2002 10:52:30 -0400 Message-ID: <1054.1018536750@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200204/138 X-Sequence-Number: 7403 writes: > When the following rule is created: > ... > then postgresql seems to be confused by the following > SQL such that psql keeps waiting for postgresql's > result: Could we see a *complete* example? It's no fun trying to reverse-engineer your table declarations from just the rule; let alone any related rules that might be involved, or the data in the table if the behavior happens to be data-dependent. regards, tom lane