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 f2QLZww68995 for ; Mon, 26 Mar 2001 16:35:58 -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 f2QLZtw00401; Mon, 26 Mar 2001 16:35:55 -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 13:25:29 -0800" Date: Mon, 26 Mar 2001 16:35:55 -0500 Message-ID: <398.985642555@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200103/540 X-Sequence-Number: 2210 "Josh Berkus" writes: >> 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. > Can you explain that? I think that the text may be short entough to be > uncompressed. Try running strings(1) on the pg_proc table, which will be ... hmm ... $PGDATA/base/YOURDBOID/1255. Look in pg_database if you're not sure of the OID of the database you are using. If you have not vacuumed then the latest version of the row will be the one closest to the front of the last 8K page of the file (got that? ;-)) regards, tom lane