-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Tried to post directy to the list but I got a bounce back. Must be too
big...
Here it is posted to my web site:
http://www.cotcomsol.com/~brock/postgresql_debug.txt
Thanks for the help,
Brock
Tom Lane wrote:
> Brock Williams <[EMAIL PROTECTED]> wri
Brock Williams <[EMAIL PROTECTED]> writes:
> I'm getting this message when I try to access one of the databases in
> my cluster:
> FATAL: cache lookup failed for access method 6881280
Unless you are using a custom index access method you didn't tell us
about, this is pretty strong evidence of da
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yep. I tried starting and stopping a couple of times. I also tried
stopping postmaster and starting a single-user mode postgres process.
Same result.
Brock
Chris Travers wrote:
> Have you tried restarting the Postmaster?
>
> Best Wishes,
> Chris T
Have you tried restarting the Postmaster?
Best Wishes,
Chris Travers
Metatron Technology Consulting
Brock Williams wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm getting this message when I try to access one of the databases in
my cluster:
FATAL: cache lookup failed for access met
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm getting this message when I try to access one of the databases in
my cluster:
FATAL: cache lookup failed for access method 6881280
I get the message any way I try to access it: remotely via TCP,
locally on the db server, as well as with a single
Christopher Browne <[EMAIL PROTECTED]> writes:
> The problem is likely that the "old tuples" are in some database not
> being vacuumed. template1 is a likely candidate; do a plain VACUUM on
> that and the message may go away.
It's not really necessary to guess about which database(s) are
triggeri
In an attempt to throw the authorities off his trail, [EMAIL PROTECTED]
("Joshua D. Drake") transmitted:
> FM wrote:
>> Hello after a vacuum full analyse I received this :
>> WARNING: some databases have not been vacuumed in 1805294030 transactions
>> HINT: Better vacuum them within 342189617 t
