Re: Thread-safe PREPARE in ecpg - Mailing list pgsql-patches

From Michael Meskes
Subject Re: Thread-safe PREPARE in ecpg
Date
Msg-id 20070925130040.GC12627@feivel.credativ.de
Whole thread Raw
In response to Thread-safe PREPARE in ecpg  (ITAGAKI Takahiro <itagaki.takahiro@oss.ntt.co.jp>)
Responses Re: Thread-safe PREPARE in ecpg  (ITAGAKI Takahiro <itagaki.takahiro@oss.ntt.co.jp>)
List pgsql-patches
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
regression suite?

> 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.

Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De, Michael at Meskes dot (De|Com|Net|Org)
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: meskes@jabber.org
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!

pgsql-patches by date:

Previous
From: Simon Riggs
Date:
Subject: Re: [HACKERS] Full page writes improvement, code update
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] 'Waiting on lock'