Re: Database OID xxxxx now seems to belong to "foo"

From: "Gauthier, Dave" <dave(dot)gauthier(at)intel(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-general(at)postgresql(dot)org>
Subject: Re: Database OID xxxxx now seems to belong to "foo"
Date: 2008-03-11 15:19:27
Message-ID: 0836165E8EE50F40A3DD8F0D87137267185FBA@azsmsx421.amr.corp.intel.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

I'm running 8.2.0 on Linux.

The postgres.conf has...

#autovacuum = off

(commented out) which lead me to believe that by default, it's on. And
I'm assuming that it's vacumming the system tables. Are these
assumptions right?

Thanks
-dave

-----Original Message-----
From: pgsql-general-owner(at)postgresql(dot)org
[mailto:pgsql-general-owner(at)postgresql(dot)org] On Behalf Of Tom Lane
Sent: Tuesday, March 11, 2008 11:10 AM
To: Gauthier, Dave
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: [GENERAL] Database OID xxxxx now seems to belong to "foo"

"Gauthier, Dave" <dave(dot)gauthier(at)intel(dot)com> writes:
> I tried vacuum pg_database, no luck. I shut down and restarted the
DB
> and it seems to have fixed the problem. Still, not sure why it
happened
> in the first place or how to prevent it in the future.

My recollection is that that's a symptom of lack of vacuuming, in PG
versions that are too old to have automatic defenses against such
DBA misfeasance. Check whether your routine vacuuming procedures
cover the system catalogs...

regards, tom lane

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2008-03-11 15:31:53 Re: Database OID xxxxx now seems to belong to "foo"
Previous Message Richard Huxton 2008-03-11 15:15:24 Re: ISO something like "#if 0 ... #endif" for SQL code