Re: Cannot use a standalone backend to VACUUM in "postgres"" - Mailing list pgsql-general

From Alvaro Herrera
Subject Re: Cannot use a standalone backend to VACUUM in "postgres""
Date
Msg-id 20080408222527.GV9062@alvh.no-ip.org
Whole thread Raw
In response to Cannot use a standalone backend to VACUUM in "postgres""  (Manuel Sugawara <masm@fciencias.unam.mx>)
List pgsql-general
Manuel Sugawara wrote:

Going back to your first message I see that I missed something
important:

> 1: relname = "pg_tablespace"    (typeid = 19, len = 64, typmod = -1, byval = f)
> 2: age = "2146484675"    (typeid = 23, len = 4, typmod = -1, byval = t)

> 1: relname = "pg_pltemplate"    (typeid = 19, len = 64, typmod = -1, byval = f)
> 2: age = "2146484675"    (typeid = 23, len = 4, typmod = -1, byval = t)

> 1: relname = "pg_shdepend"    (typeid = 19, len = 64, typmod = -1, byval = f)
> 2: age = "2146484675"    (typeid = 23, len = 4, typmod = -1, byval = t)

> 1: relname = "pg_shdescription"    (typeid = 19, len = 64, typmod = -1, byval = f)
> 2: age = "2146484675"    (typeid = 23, len = 4, typmod = -1, byval = t)

> 1: relname = "pg_database"    (typeid = 19, len = 64, typmod = -1, byval = f)
> 2: age = "2146484675"    (typeid = 23, len = 4, typmod = -1, byval = t)

> 1: relname = "pg_auth_members"    (typeid = 19, len = 64, typmod = -1, byval = f)
> 2: age = "2146484675"    (typeid = 23, len = 4, typmod = -1, byval = t)

These are all shared catalogs AFAIR.  Have you vacuumed those?

--
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

pgsql-general by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Cannot use a standalone backend to VACUUM in "postgres""
Next
From: Tom Lane
Date:
Subject: Re: More SSL crash woes