Re: Attaching database - Mailing list pgsql-general

From Peter J. Holzer
Subject Re: Attaching database
Date
Msg-id 20201025182653.GA11390@hjp.at
Whole thread Raw
In response to Re: Attaching database  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: Attaching database  (Igor Korot <ikorot01@gmail.com>)
List pgsql-general
On 2020-10-19 20:21:05 +0200, Pavel Stehule wrote:
> po 19. 10. 2020 v 20:18 odesílatel Igor Korot <ikorot01@gmail.com> napsal:
>     On Mon, Oct 19, 2020 at 12:51 PM Pavel Stehule <pavel.stehule@gmail.com>
>     wrote:
>     > It is a different thing - postgresql_fdw does nested connect - it uses
>     > client-server protocol.
>     >
>     > For postgres connect and sql engine process is one entity - and engine is
>     > written without a possibility to reconnect to another database.
>
>     So if I understand correctly the postgresql_fdw is creating a second
>     connection and uses it as kind of "virtualizing mechanism"
>     in order to give access to the second database.
>
>
> yes - it does new connect to somewhere (local or remote server, but mechanism
> is absolutely same)

In case this isn't clear:

It is the server (or more specifically, the foreign data wrapper) which
opens that connection. To the client it looks like it's just accessing a
normal table within the same database.

        hp

--
   _  | Peter J. Holzer    | Story must make more sense than reality.
|_|_) |                    |
| |   | hjp@hjp.at         |    -- Charles Stross, "Creative writing
__/   | http://www.hjp.at/ |       challenge!"

Attachment

pgsql-general by date:

Previous
From: Andreas Kretschmer
Date:
Subject: Re: Feature Requests
Next
From: Ayub M
Date:
Subject: Re: postgres materialized view refresh performance