Re: Database OID xxxxx now seems to belong to "foo" - Mailing list pgsql-general

From Gauthier, Dave
Subject Re: Database OID xxxxx now seems to belong to "foo"
Date
Msg-id 0836165E8EE50F40A3DD8F0D87137267185FBA@azsmsx421.amr.corp.intel.com
Whole thread Raw
In response to Database OID xxxxx now seems to belong to "foo"  ("Gauthier, Dave" <dave.gauthier@intel.com>)
Responses Re: Database OID xxxxx now seems to belong to "foo"  (Alvaro Herrera <alvherre@commandprompt.com>)
List 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@postgresql.org
[mailto:pgsql-general-owner@postgresql.org] On Behalf Of Tom Lane
Sent: Tuesday, March 11, 2008 11:10 AM
To: Gauthier, Dave
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Database OID xxxxx now seems to belong to "foo"

"Gauthier, Dave" <dave.gauthier@intel.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

--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

pgsql-general by date:

Previous
From: Richard Huxton
Date:
Subject: Re: ISO something like "#if 0 ... #endif" for SQL code
Next
From: Tom Lane
Date:
Subject: Re: Database OID xxxxx now seems to belong to "foo"