| From: | Magnus Hagander <mha(at)sollentuna(dot)net> |
|---|---|
| To: | "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Ross J(dot) Reedstrom" <reedstrm(at)wallace(dot)ece(dot)rice(dot)edu> |
| Cc: | pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | RE: [HACKERS] Threads |
| Date: | 1999-08-03 16:34:52 |
| Message-ID: | 215896B6B5E1CF11BC5600805FFEA82101F70BF4@sirius.edu.sollentuna.se |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
:
> > 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.
Hmm. Really?
AFAIK, only:
pgresStatus[]
is exported, and that one is a) read-only and b) deprecated, and replaced
with a function.
No?
Otherwise, I've been darn lucky in the multithreaded stuff I have :-) (I run
with a different PGconn for each thread, and the PGresult:s are protected by
CriticalSections (this is Win32)). And if that's it, then I really need to
fix it...
//Magnus
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 1999-08-03 16:48:17 | Re: [HACKERS] pg_upgrade may be mortally wounded |
| Previous Message | Magnus Hagander | 1999-08-03 16:20:19 | RE: [HACKERS] Threads |