> -----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; [email protected]
> Subject: Re: [GENERAL] Dropping a database that does not exist
>
> 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.
>
> > 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
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
