| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Igor Korot <ikorot01(at)gmail(dot)com>, "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | "Peter J(dot) Holzer" <hjp-pgsql(at)hjp(dot)at>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Attaching database |
| Date: | 2022-10-15 15:51:41 |
| Message-ID: | 5fbcdf5a-aad8-d927-b547-263db23fca2e@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 10/15/22 08:20, Adrian Klaver wrote:
> On 10/14/22 21:46, Igor Korot wrote:
>
>
>> Making catalog current means switching between DBs.
>> Remember initially I connected to (finance) DB, which made the
>> (finance) catalog
>> current.
>> Then I "opened a second connection" to (finance_2021), which made
>> that current catalog and so that select would give me all tables from
>> (finance_2021).
>
> No you didn't.
>
> Rough outline of what happens:
>
> 1) You connected to the database finance.
> 2) While in the finance database you queried the foreign tables that are
> linked to finance_2021.
> 3) The queries made connections the to finance_2021 for the purposes of
> making the data visible in the foreign tables in finance.
> 4) The client you did this did not 'leave' the finance database, so the
^
in
> only information_schema you have access to is in the finance database.
>
>>
>> I hope now its clearer.
>>
>> Thank you.
>>
>>>
>>> David J.
>>
>>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Igor Korot | 2022-10-15 15:56:32 | Re: Attaching database |
| Previous Message | Adrian Klaver | 2022-10-15 15:20:55 | Re: Attaching database |