| From: | Duane Currie <dcurrie(at)sandman(dot)acadiau(dot)ca> |
|---|---|
| To: | tgl(at)sss(dot)pgh(dot)pa(dot)us (Tom Lane) |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [HACKERS] Threads |
| Date: | 1999-08-03 13:33:44 |
| Message-ID: | 199908031333.KAA08666@sandman.acadiau.ca |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> "Ross J. Reedstrom" <reedstrm(at)wallace(dot)ece(dot)rice(dot)edu> writes:
> > Hmm, what about threads in the frontend? Anyone know if libpq is thread
> > safe, and if not, how hard it might be to make it so?
>
> It is not; the main reason why not is a brain-dead part of the API that
> exposes modifiable global variables. Check the mail list archives
> (probably psql-interfaces, but maybe -hackers) for previous discussions
> with details. Earlier this year I think, or maybe late 98.
hmmm... usually this is repairable by creating wrapper functions which
index the variables by thread id, and enforcing the use of the functions...
(maybe something for a wish list...)
Duane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 1999-08-03 14:03:47 | Re: [HACKERS] pg_upgrade may be mortally wounded |
| Previous Message | Duane Currie | 1999-08-03 11:44:01 | Re: [HACKERS] Threads |