| From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
|---|---|
| To: | <pgsql-odbc(at)postgresql(dot)org> |
| Cc: | "Anoop Kumar" <anoopk(at)pervasive-postgres(dot)com> |
| Subject: | Re: Libpq driver: thread problem |
| Date: | 2005-07-14 12:08:31 |
| Message-ID: | E7F85A1B5FF8D44C8A1AF6885BC9A0E4AC9238@ratbert.vale-housing.co.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-odbc |
> -----Original Message-----
> From: pgsql-odbc-owner(at)postgresql(dot)org
> [mailto:pgsql-odbc-owner(at)postgresql(dot)org] On Behalf Of Dave Page
> Sent: 14 July 2005 12:06
> To: pgsql-odbc(at)postgresql(dot)org
> Cc: Anoop Kumar
> Subject: [ODBC] Libpq driver: thread problem
>
> One thing to note, the Windows Port of PostgreSQL has never
> worked with
> the --enable-thread-safety option. This has never been a problem for
> pgAdmin (for example), but may be here.
After some discussion with Magnus Hagander, that is probably a red
herring. He recalls that --enable-thread-safety is needed on platforms
that don't have a thread safe API already - windows does as I'm sure you
know.
Regards, Dave
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joel Fradkin | 2005-07-14 15:41:58 | Re: Benchmark results |
| Previous Message | Dave Page | 2005-07-14 11:05:32 | Libpq driver: thread problem |