From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Michael Meskes <meskes(at)postgresql(dot)org> |
Cc: | Leif Jensen <leif(at)crysberg(dot)dk>, pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: ECPG SET CONNECTION |
Date: | 2015-05-15 14:40:29 |
Message-ID: | 20150515144029.GL23739@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Fri, May 15, 2015 at 01:10:27PM +0200, Michael Meskes wrote:
> On 14.05.2015 19:35, Bruce Momjian wrote:
> > On Fri, May 31, 2013 at 02:26:08PM +0200, Leif Jensen wrote:
> >> Hi guys.
> >>
> >> In the ECPG manual (including latest 9.1.9) about ECPG SQL SET CONNECTION <connection name>; it is stated that "This is not thread-aware".
> >>
> >> When looking in the ecpg library code connect.c for ECPGsetconn( ... ), it looks very much like it is thread-aware if translated with the --enable-thread-safety option.
> >>
> >> What should I believe ?
> >
> > Can someone comment on this report from 2013?
>
> Sorry, it seems I missed this email. Yes, the code should be
> thread-aware, at least I don't know of any problems with it. It appears
> to me that the docs haven't been updated by the patch that made ecpg
> work with threads back in the day.
Thanks. Is that the only doc line that needs adjustment?
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ Everyone has their own god. +
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2015-05-15 14:49:43 | Re: pg_upgrade failing from 9.3 to 9.4 because "template0" already exists |
Previous Message | Dennis | 2015-05-15 13:38:29 | Re: BDR table level replication questions |