Received: from davinci.ethosmedia.com (davinci.ethosmedia.com [209.10.40.250] (may be forged)) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f2JG8B344240 for ; Mon, 19 Mar 2001 11:08:11 -0500 (EST) (envelope-from josh@agliodbs.com) Received: from [209.10.40.250] (account ) by davinci.ethosmedia.com (CommuniGate Pro WebUser 3.4.1) with HTTP id 26601; Mon, 19 Mar 2001 08:05:41 -0800 From: "Josh Berkus" Subject: Re: What do I do with this error? To: Tom Lane Cc: pgsql-sql@postgresql.org X-Mailer: CommuniGate Pro Web Mailer v.3.4.1 Date: Mon, 19 Mar 2001 08:05:41 -0800 Message-ID: In-Reply-To: <8897.984975741@sss.pgh.pa.us> MIME-Version: 1.0 Content-Type: text/plain; charset="ISO-8859-1" Content-Transfer-Encoding: 8bit X-Archive-Number: 200103/359 X-Sequence-Number: 2023 Tom, Stephan: I was hoping that the error would be reproduceable with a simplified example; however, it looks like I'll have to supply you folks with the full function an tabledefs. I hesitated to do so, because the function involves doing a pattern-matching search based on a complex view linked to an IN search on a subtable. It's no doubt this combination of factors that's making things blow up. BTW, I found an easy workaround for the problem; I'm pursuing this just as a beta issue for PgSQL 7.1. Can either of you supply me with syntax to pg_dump the full function & view decarations to a text file? I'm using pgaccess mostly for development, but it doesn' let me cut-and-paste. -Josh Berkus