Skip site navigation (1) Skip section navigation (2)

Re: Dropping a database that does not exist

From: Tham Shiming <shiming(at)misatravel(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Dave Page <dpage(at)vale-housing(dot)co(dot)uk>, "Uwe C(dot) Schroeder" <uwe(at)oss4u(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: Dropping a database that does not exist
Date: 2006-02-15 01:16:59
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-general
 From pg_controldata

Latest checkpoint NextXID: 746940488

Under the database tree that is displayed in pgAdmin, when I click on 
the database, an error dialog pops up with this message "An error has 
occured: FATAL: database "db2" does not exist". Even if I disconnect and 
reconnect, the database tree still shows db2 but if I just click on it, 
the same error dialog will appear.


Tom Lane wrote:
> Tham Shiming <shiming(at)misatravel(dot)com> writes:
>> ctid(tid)   xmin(xid)   xmax(xid)   datname(name)
>> (0,5)       2           2213800494  db2 (pgAdmin says this DB does not 
>> exist)
>> (0,8)       2           2214815770  db3 (pgAdmin says this DB does not 
>> exist)
>> (0,10)      2           2213853192  db5 (repeat)
>> (0,13)      2           0           db5 (repeat)
> This does start to look like an XID wraparound problem.  What is your
> current XID counter?  (The "NextXID" line from pg_controldata output
> is close enough.)  What *exactly* do you mean by "pgAdmin says this
> DB does not exist"?
> 			regards, tom lane

In response to

pgsql-general by date

Next:From: Ken WinterDate: 2006-02-15 04:52:27
Subject: Does PG really lack a time zone for India?
Previous:From: Michael FuhrDate: 2006-02-14 23:13:29
Subject: Re: stateful UDF?

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group