Dear Meskes,
From: pgsql-hackers-ow...@postgresql.org
> [mailto:pgsql-hackers-ow...@postgresql.org] On Behalf Of Michael Meskes
> Done.
Thanks, I confirmed the commit messages.
> My standard workflow is to wait a couple days to see if everything works
> nicely before backporting. Obviously
On Wed, Jun 07, 2017 at 03:45:23AM +, Tsunakawa, Takayuki wrote:
> Could you also apply it to past versions if you don't mind? The oldest
> supported version 9.2 is already thread-aware.
Done.
My standard workflow is to wait a couple days to see if everything works nicely
before
From: pgsql-hackers-ow...@postgresql.org
> [mailto:pgsql-hackers-ow...@postgresql.org] On Behalf Of Michael Meskes
> I'm pretty sure it is indeed thread-aware, although I didn't provide the
> code for this feature myself.
>
> > So the doc seems to need fix. The patch is attached.
>
> Thanks,
Dear Tsunakawa-san,
sorry for the late reply, I've been traveling all of last week and only
just came back.
>> What does this mean by "not thread-aware?" Does SET CONNECTION in one
>> thread change the current connection in another thread?
>> It doesn't look so, because the connection
From: pgsql-hackers-ow...@postgresql.org
> [mailto:pgsql-hackers-ow...@postgresql.org] On Behalf Of Tsunakawa,
> Takayuki
> The following page says:
>
> https://www.postgresql.org/docs/devel/static/ecpg-connect.html#ecpg-se
> t-connection
>
> --
>
Hello,
The following page says:
https://www.postgresql.org/docs/devel/static/ecpg-connect.html#ecpg-set-connection
--
EXEC SQL AT connection-name SELECT ...;
If your application uses multiple threads of execution, they cannot share a
connection
