From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Igor Korot <ikorot01(at)gmail(dot)com> |
Cc: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>, "Peter J(dot) Holzer" <hjp-pgsql(at)hjp(dot)at>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Attaching database |
Date: | 2022-10-15 16:10:00 |
Message-ID: | 74596570-bd32-c970-6d2a-14305cd47d24@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 10/15/22 08:56, Igor Korot wrote:
> Hi, Adrian,
>
>
> So any and all operations/queries performed before, during or after that
> will be done on (finance) catalog), because this is the "main"
> connection, right?
>
I think you are getting stuck on SQLite terminology:
https://sqlite.org/lang_attach.html
"Transactions involving multiple attached databases are atomic, assuming
that the main database is not ":memory:" and the journal_mode is not
WAL. ..."
That is different mechanism all together.
The closest I can come with alternate example is linked tables in Access.
You are working in one client connected to Server A that makes as needed
connections to Server B to move data back and forth. You are not
actually connected full time to Server B and your point of reference is
the connection your client initially made to Server A. So yes because it
is the "main" connection.
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Alex Theodossis | 2022-10-15 22:57:31 | Re: Attaching database |
Previous Message | Igor Korot | 2022-10-15 15:56:32 | Re: Attaching database |