From: Tom Lane <tgl@sss.pgh.pa.us>
To: Josh Berkus <josh@agliodbs.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: Function Vanished
Date: Mon, 26 Mar 2001 16:35:55 -0500
Message-ID: <398.985642555@sss.pgh.pa.us> (raw)
In-Reply-To: <web-30069@davinci.ethosmedia.com>
References: <web-30069@davinci.ethosmedia.com>
"Josh Berkus" <josh@agliodbs.com> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-sql@postgresql.org
Cc: tgl@sss.pgh.pa.us, josh@agliodbs.com
Subject: Re: Function Vanished
In-Reply-To: <398.985642555@sss.pgh.pa.us>
References: <web-30069@davinci.ethosmedia.com> <398.985642555@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox