On Tue, Sep 25, 2007 at 03:22:13PM +0900, ITAGAKI Takahiro wrote:
> Here is a WIP patch to make prepared statements thread-safe in ecpg.
> The variable prep_stmts was global but not protected by any locks.
> I divided it into per-connection field so that we can access prepared
> statements separately in each thread.
Thanks a lot. This is exactly how I was planning to implement it, but I
haven't even found the time to start coding yet. :-)
Could you please create a small example that we could add to the
> I needed to change the following exported functions, but it will
> introduce an incompatibility issue. It might be ok for CVS HEAD,
> but I'd like to port the fix to back versions. Do you have any
> thoughts on how we can accomplish this better?
No idea at the moment, sorry.
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: meskes(at)jabber(dot)org
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
In response to
pgsql-hackers by date
|Next:||From: Kenneth Marshall||Date: 2007-09-25 13:17:16|
|Subject: Re: Hash index todo list item|
|Previous:||From: Michael Meskes||Date: 2007-09-25 12:58:15|
|Subject: Re: MSVC build scripts status|
pgsql-patches by date
|Next:||From: Tom Lane||Date: 2007-09-25 13:16:53|
|Subject: Re: [HACKERS] 'Waiting on lock' |
|Previous:||From: Simon Riggs||Date: 2007-09-25 09:29:24|
|Subject: Re: [HACKERS] Full page writes improvement, code update|