From: | Michael Meskes <meskes(at)postgresql(dot)org> |
---|---|
To: | "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)jp(dot)fujitsu(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Is ECPG's SET CONNECTION really not thread-aware? |
Date: | 2017-06-06 10:20:19 |
Message-ID: | 2ad9bb57-8ea4-483b-99d4-303d1ce7e29e@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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 management and SQL execution
>> in ECPG uses thread-specific data (TSD) to get and set the current connection,
>> like this:
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, applied.
Michael
--
Michael Meskes
Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
Meskes at (Debian|Postgresql) dot Org
Jabber: michael at xmpp dot meskes dot org
VfL Borussia! Força Barça! Go SF 49ers! Use Debian GNU/Linux, PostgreSQL
From | Date | Subject | |
---|---|---|---|
Next Message | Rafia Sabih | 2017-06-06 10:29:30 | Re: Proposal : For Auto-Prewarm. |
Previous Message | Neha Sharma | 2017-06-06 10:18:02 | Re: Proposal : For Auto-Prewarm. |