Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154]) by mail.postgresql.org (8.11.3/8.11.1) with ESMTP id f2QL9Iw65840 for ; Mon, 26 Mar 2001 16:09:18 -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.3/8.11.3) with ESMTP id f2QL9Fw00295; Mon, 26 Mar 2001 16:09:15 -0500 (EST) To: "Josh Berkus" cc: pgsql-sql@postgresql.org Subject: Re: Function Vanished In-reply-to: References: Comments: In-reply-to "Josh Berkus" message dated "Mon, 26 Mar 2001 11:55:59 -0800" Date: Mon, 26 Mar 2001 16:09:14 -0500 Message-ID: <292.985640954@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200103/537 X-Sequence-Number: 2207 "Josh Berkus" writes: > I'm using 7.1 Beta 3, which has been pretty stable up until now. This > morning, I went to export a function I spent 5 hours debugging on on > Friday to text so that I could have a copy of the final version. To my > horror, the function was GONE from the system catalog (pg_proc). Ick. Were you maybe working on it inside a transaction that you forgot to commit? > I have > not run VACUUM on the database anytime recently ... is there any > possibility that my function is still present as a "deleted" row? Should still be there in the table, if you haven't vacuumed. Getting it out again is another story though. If it was a small enough function, good ol' "strings" would do to extract the function body, which is probably all that you really need. But if it's more than a couple K then the text will be compressed and difficult to spot or extract. regards, tom lane