| From: | Igor Korot <ikorot01(at)gmail(dot)com> |
|---|---|
| To: | Christophe Pettus <xof(at)thebuild(dot)com> |
| Cc: | Erik Wienhold <ewie(at)ewie(dot)name>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Get table catalog from pg_indexes |
| Date: | 2022-11-27 18:53:18 |
| Message-ID: | CA+FnnTz7pQgJJOFN27muDKN3zauJEj=gtYUSYqkrV-cB-GsfqQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi, Christopher,
On Sun, Nov 27, 2022 at 12:45 PM Christophe Pettus <xof(at)thebuild(dot)com> wrote:
>
>
>
> > On Nov 27, 2022, at 10:42, Igor Korot <ikorot01(at)gmail(dot)com> wrote:
> >
> > It doesn't say anything about "current" DB - only the DB.
>
> In PostgreSQL terminology, a single PostgreSQL instance (the cluster) can have multiple databases.
Just like any other DBMS.
> The database the connection is currently open to is the current database.
Are you saying I can't run any query on other DB? Or connect to DB and
run select?
Thank you.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2022-11-27 18:54:47 | Re: Get table catalog from pg_indexes |
| Previous Message | Christophe Pettus | 2022-11-27 18:44:22 | Re: Get table catalog from pg_indexes |