| From: | "Michael J(dot) Baars" <mjbaars1977(dot)pgsql(dot)hackers(at)gmail(dot)com> |
|---|---|
| To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: libpq and multi-threading |
| Date: | 2023-05-02 16:09:05 |
| Message-ID: | CAMHx2Rs7bGPNoAs2cGJ0kA-vrn7PPqFk+Ro8fc1mbBkK4Za8RQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Hi David,
My mistake. Too much fiddling around, but better than no fiddling around.
It appears both sides make mistakes, or does your freely passing around
work better than mine?
On Tue, 2 May 2023, 17:57 David G. Johnston, <david(dot)g(dot)johnston(at)gmail(dot)com>
wrote:
> On Tue, May 2, 2023 at 2:38 AM Michael J. Baars <
> mjbaars1977(dot)pgsql(dot)hackers(at)gmail(dot)com> wrote:
>
>> I have already tried to set the PostgreSQL 'dynamic_shared_memory_type'
>> configuration option to 'mmap', but this does not help.
>>
>>
> Of course it doesn't, that is a server-side configuration.
>
> "Specifies the dynamic shared memory implementation that the server should
> use."
>
>
> https://www.postgresql.org/docs/current/runtime-config-resource.html#RUNTIME-CONFIG-RESOURCE-MEMORY
>
> David J.
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter J. Holzer | 2023-05-02 17:57:59 | Re: libpq and multi-threading |
| Previous Message | David G. Johnston | 2023-05-02 15:57:14 | Re: libpq and multi-threading |