Received: from sss.pgh.pa.us (unknown [192.204.191.242]) by postgresql.org (Postfix) with ESMTP id 79F93475892 for ; Fri, 12 Apr 2002 13:32:54 -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 g3CHWqF28204; Fri, 12 Apr 2002 13:32:52 -0400 (EDT) To: cnliou@eurosport.com Cc: pgsql-sql@postgresql.org Subject: Re: Problem With A Rule (clear version) In-reply-to: <200204121050.31c2@th00.opsion.fr> References: <200204121050.31c2@th00.opsion.fr> Comments: In-reply-to message dated "Fri, 12 Apr 2002 10:50:49 +0000" Date: Fri, 12 Apr 2002 13:32:51 -0400 Message-ID: <28201.1018632771@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200204/155 X-Sequence-Number: 7419 writes: > I am afraid that this too-complete example makes > readers headache. I'm afraid you omitted some detail that's necessary to show the problem ... because it works fine for me. Please try to make a pg_dump script that can be loaded into a fresh database to produce the problem. I'm not willing to hand-edit SELECT output into INSERT statements again. regards, tom lane