Re: [GENERAL] Dropping a database that does not exist

2006-02-15 Thread Tham Shiming
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

Re: [GENERAL] Dropping a database that does not exist

2006-02-14 Thread Tom Lane
Tham Shiming <[EMAIL PROTECTED]> 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 db

Re: [GENERAL] Dropping a database that does not exist

2006-02-14 Thread Tham Shiming
Sorry, I wasn't being clear. For the sample output from pgAdmin below, I just did a select * from pg_database, then just typed out the 2 columns that I thought would be relevant. OK, here's the output for select ctid, xmin, xmax, datname from pg_database; ctid(tid) xmin(xid) xmax(xid) da

Re: [GENERAL] Dropping a database that does not exist

2006-02-13 Thread Tom Lane
"Dave Page" writes: >> Tham Shiming <[EMAIL PROTECTED]> writes: >>> OK, checking pg_shadow, the usesysid for each entry is unique. >>> pg_database, however, showed the duplicate databases. A >>> short sample output from pgAdmin. >>> >>> datnamedatdba >>> db1101 >>> db1101 >>

Re: [GENERAL] Dropping a database that does not exist

2006-02-13 Thread Dave Page
> -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Tom Lane > Sent: 13 February 2006 14:36 > To: Tham Shiming > Cc: Uwe C. Schroeder; pgsql-general@postgresql.org > Subject: Re: [GENERAL] Dropping a database that does not exi

Re: [GENERAL] Dropping a database that does not exist

2006-02-13 Thread Tom Lane
Tham Shiming <[EMAIL PROTECTED]> writes: > OK, checking pg_shadow, the usesysid for each entry is unique. > pg_database, however, showed the duplicate databases. A short sample > output from pgAdmin. > datnamedatdba > db1101 > db1101 > db2102 > db3103 > db3

Re: [GENERAL] Dropping a database that does not exist

2006-02-13 Thread Tham Shiming
Well, not exactly support. We didn't create the duplicate databases, it just appear suddenly out of nowhere, which was also odd. OK, checking pg_shadow, the usesysid for each entry is unique. pg_database, however, showed the duplicate databases. A short sample output from pgAdmin. datname

Re: [GENERAL] Dropping a database that does not exist

2006-02-10 Thread Tom Lane
"Uwe C. Schroeder" <[EMAIL PROTECTED]> writes: > I don't think you have duplicate databases - that would be the first time I > heard that postgreSQL supports that. > Are you sure you didn't create the database with a name that just doesn't > print? That's one possibility that I was wondering abo

Re: [GENERAL] Dropping a database that does not exist

2006-02-10 Thread Uwe C. Schroeder
I don't think you have duplicate databases - that would be the first time I heard that postgreSQL supports that. Are you sure you didn't create the database with a name that just doesn't print? I.e. a simple createdb test works. do another createdb "test " (note the space) works too, but when

Re: [GENERAL] Dropping a database that does not exist

2006-02-10 Thread Tom Lane
Tham Shiming <[EMAIL PROTECTED]> writes: > I've been getting duplicate databases within my server. What exactly makes you think you have that? regards, tom lane ---(end of broadcast)--- TIP 5: don't forget to increase your f

[GENERAL] Dropping a database that does not exist

2006-02-10 Thread Tham Shiming
Hi, I've been getting duplicate databases within my server. Dropping one of them works, but when I try to drop the other, psql will say that the database does not exist. For example: db1 db1 db2 db3 db4 db4 db5 Running DROP DATABASE db1 for the first time works and I'm left with: db1 db2 d