From: | Stelios Sfakianakis <sgsfak(at)gmail(dot)com> |
---|---|
To: | Ian Lawrence Barwick <barwick(at)gmail(dot)com> |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Keeping state in a foreign data wrapper |
Date: | 2020-08-04 10:21:36 |
Message-ID: | 113D4B17-B9EA-425A-896C-0095C73FDF8C@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Thank you again, I have another question in order to make sure I have a clear understanding:
> On 4 Aug 2020, at 11:24, Ian Lawrence Barwick <barwick(at)gmail(dot)com> wrote:
>
> The hash table is specific to each running backend so will only be
> accessed by that process.
>
> Pre-loading a shared library just gives the library an opportunity to
> set up shared memory etc. You can always try adding one of the FDW
> libraries to "shared_preload_libraries" and see what happens
> (theoretically nothing).
>
My impression was that since each client (e.g. libpq) connection results in the creation of a Postgres process in the backend (https://www.postgresql.org/developer/backend/) then this (mysql) "connection pool" hash table is not global per se and shared among the different client / users sessions. But that defeats the purpose, no?
Thank you
Best
Stelios
From | Date | Subject | |
---|---|---|---|
Next Message | Tony Shelver | 2020-08-04 12:09:42 | Re: Querying PostgreSQL / PostGIS Databases in Python |
Previous Message | Srinivasa T N | 2020-08-04 09:39:26 | Re: Unexplained disk usage in AWS Aurora Postgres |