Re: Cannot use a standalone backend to VACUUM in "postgres""

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