Received: from orion.SAPserv.Hamburg.dsh.de (Tpolaris2.sapham.debis.de [53.2.131.8]) by hub.org (8.9.3/8.9.3) with SMTP id IAA87329; Fri, 25 Jun 1999 08:09:45 -0400 (EDT) (envelope-from wieck@debis.com) Received: by orion.SAPserv.Hamburg.dsh.de for pgsql-hackers@postgreSQL.org id m10xUnQ-0003kvC; Fri, 25 Jun 99 14:09 MET DST Message-Id: From: wieck@debis.com (Jan Wieck) Subject: Re: [HACKERS] Re: trouble creating log table with rules To: wayne@senet.com.au (Wayne Piekarski) Date: Fri, 25 Jun 1999 14:09:28 +0200 (MET DST) Cc: pgsql-sql@postgreSQL.org, pgsql-hackers@postgreSQL.org, jmr@computing.com Reply-To: jwieck@debis.com (Jan Wieck) In-Reply-To: <199906250652.QAA29938@helpdesk.senet.com.au> from "Wayne Piekarski" at Jun 25, 99 04:22:36 pm X-Mailer: ELM [version 2.4 PL25] Content-Type: text > > > Date: Thu, 24 Jun 1999 01:53:05 -0500 > > From: Jim Rowan > > Subject: trouble creating log table with rules > > > > I've read the docs in the programmers manual, and can create rules like this: > > > > CREATE RULE "m_log_change" AS ON UPDATE TO "machine" > > do ( > > INSERT INTO machine_log (who, date, machnum, col, newval) > > SELECT getpgusername(), 'now'::text, old.machnum, > > 'host', new.host > > WHERE (new.host != old.host) or > > (old.host IS NOT NULL and new.host IS NULL) or > > (old.host IS NULL and new.host IS NOT NULL); > > > > INSERT INTO machine_log (who, date, machnum, col, newval) > > SELECT getpgusername(), 'now'::text, old.machnum, > > 'serial_num_cpu', new.serial_num_cpu > > WHERE (new.serial_num_cpu != old.serial_num_cpu) or > > (old.serial_num_cpu IS NOT NULL and new.serial_num_cpu IS NULL) or > > (old.serial_num_cpu IS NULL and new.serial_num_cpu IS NOT NULL); > > ); > > > > My big problem is that if I replicate this enough times to cover the fields I > > want, I get this error: > > > > pqReadData() -- backend closed the channel unexpectedly. > > This probably means the backend terminated abnormally > > before or while processing the request. > > We have lost the connection to the backend, so further processing is impossible. Terminating. > > You didn't tell us which version of PostgreSQL and (more important) if the error occurs during CREATE RULE or when updating machine. If it occurs during the CREATE RULE (what I hope for you) it doesn't happen in the rewriter itself. For the rule actions in the example above it isn't important in which order they are processed. So you could setup single action rules per field to get (mostly) the same results. If you can create the entire multi action rule but get the backend crash during UPDATE of machine, then it's a problem in the rewriter which I cannot imagine looking at your rules. Jan -- #======================================================================# # It's easier to get forgiveness for being wrong than for being right. # # Let's break this rule - forgive me. # #========================================= wieck@debis.com (Jan Wieck) #