Re: Dropping a database that does not exist

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Tham Shiming" <shiming(at)misatravel(dot)com>
Cc: "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-13 14:44:20
Message-ID: E7F85A1B5FF8D44C8A1AF6885BC9A0E40103E081@ratbert.vale-housing.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> -----Original Message-----
> From: pgsql-general-owner(at)postgresql(dot)org
> [mailto:pgsql-general-owner(at)postgresql(dot)org] On Behalf Of Tom Lane
> Sent: 13 February 2006 14:36
> To: Tham Shiming
> Cc: Uwe C. Schroeder; pgsql-general(at)postgresql(dot)org
> Subject: Re: [GENERAL] Dropping a database that does not exist
>
> Tham Shiming <shiming(at)misatravel(dot)com> 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.
>
> > datname datdba
> > db1 101
> > db1 101
> > db2 102
> > db3 103
> > db3 103
>
> Does anyone know what the underlying query is that pgadmin uses for
> this display?

pgAdmin wouldn't display anything like that unless the user entered the
query themselves, or did a 'view data' on pg_database (in which case it
would just be a select *, possibly with a user entered WHERE restriction
or an ORDER BY).

Regards, Dave

Responses

Browse pgsql-general by date

  From Date Subject
Next Message sualeh.fatehi 2006-02-13 14:48:59 Re: Database Comparison tool?
Previous Message Tom Lane 2006-02-13 14:35:36 Re: Dropping a database that does not exist