Re: Dropping a database that does not exist
От | Dave Page |
---|---|
Тема | Re: Dropping a database that does not exist |
Дата | |
Msg-id | E7F85A1B5FF8D44C8A1AF6885BC9A0E40103E081@ratbert.vale-housing.co.uk обсуждение исходный текст |
Ответ на | Dropping a database that does not exist (Tham Shiming <shiming@misatravel.com>) |
Ответы |
Re: Dropping a database that does not exist
|
Список | pgsql-general |
> -----Original Message----- > From: pgsql-general-owner@postgresql.org > [mailto:pgsql-general-owner@postgresql.org] 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 exist > > Tham Shiming <shiming@misatravel.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
В списке pgsql-general по дате отправления: