Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.4) with ESMTP id g1GK2CE10282 for ; Sat, 16 Feb 2002 15:02:12 -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.4/8.11.4) with ESMTP id g1GK2Cf21220; Sat, 16 Feb 2002 15:02:12 -0500 (EST) To: "Josh Berkus" cc: pgsql-sql@postgresql.org Subject: Re: More problems with 7.2 & functions In-reply-to: References: Comments: In-reply-to "Josh Berkus" message dated "Sat, 16 Feb 2002 11:58:05 -0800" Date: Sat, 16 Feb 2002 15:02:12 -0500 Message-ID: <21217.1013889732@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200202/202 X-Sequence-Number: 6627 "Josh Berkus" writes: > However, the bug is NOT reproduceable with a less complex model -- > possibly not reproduceable on any other database. I have tried to > reproduce it using a simpler view that I could post to you, and I > can't. Since I can't give you the whole database at this time (IP > agreements), Understood, but this is a planning-time issue so I don't actually need any data. Just the schema (and possibly the functions). Can you strip down the number of tables involved and/or rename tables and columns enough to address your IP worries? regards, tom lane