Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id eB1M7XF26341; Fri, 1 Dec 2000 17:07:33 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.1/8.11.1) with ESMTP id eB1M7gY15320; Fri, 1 Dec 2000 17:07:42 -0500 (EST) To: "Joel Burton" cc: pgsql-hackers@postgresql.org, pgsql-sql@postgresql.org Subject: Re: Rules with Conditions: Bug, or Misunderstanding In-reply-to: <3A27CBE2.20547.491631@localhost> References: <3A255246.21430.688927F3@localhost> <3A27CBE2.20547.491631@localhost> Comments: In-reply-to "Joel Burton" message dated "Fri, 01 Dec 2000 16:03:46 -0500" Date: Fri, 01 Dec 2000 17:07:42 -0500 Message-ID: <15317.975708462@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200012/7 X-Sequence-Number: 338 "Joel Burton" writes: > In any event, though, the rule above crashes my backend, as do > simpler versions I wrote that try your CREATE RULE DO INSTEAD ( > INSERT; UPDATE; ) idea. Ugh :-( > What information can I provide to the list to troubleshoot this? A gdb backtrace from the corefile, and/or a simple example to replicate the problem... regards, tom lane