Received: from mail1.hub.org (webmail.hub.org [216.126.85.1]) by mail.postgresql.org (8.11.3/8.11.1) with ESMTP id f2JHXAN00802 for ; Mon, 19 Mar 2001 12:33:11 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154]) by mail1.hub.org (8.11.3/8.11.1) with ESMTP id f2JHX9c00784 for ; Mon, 19 Mar 2001 12:33:09 -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 f2JHWwt20237; Mon, 19 Mar 2001 12:32:58 -0500 (EST) To: "Josh Berkus" cc: pgsql-sql@postgresql.org Subject: Re: What do I do with this error? In-reply-to: References: Comments: In-reply-to "Josh Berkus" message dated "Mon, 19 Mar 2001 08:05:41 -0800" Date: Mon, 19 Mar 2001 12:32:57 -0500 Message-ID: <20234.985023177@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200103/361 X-Sequence-Number: 2025 "Josh Berkus" writes: > 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. Possibly, or it could be dependent on platform or configuration factors. What platform/configure options/locale/etc are you using? regards, tom lane