| From: | Magnus Hagander <magnus(at)hagander(dot)net> |
|---|---|
| To: | PGSQL-Patches <pgsql-patches(at)postgresql(dot)org> |
| Subject: | ecpg threading vs win32 |
| Date: | 2007-03-17 22:18:01 |
| Message-ID: | 45FC6919.1090702@hagander.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
This patch replaces the pthreads code in ecpg with native win32 threads,
in order to make it threadsafe. The idea is not to have to download the
non-standard pthreads library on windows.
Does it seem like it should be doing the right thing? Does somebody have
a good test-case where ecpg breaks when not built thread-safe? (which
would then also break when built thread-safe with a broken implementation)
//Magnus
| Attachment | Content-Type | Size |
|---|---|---|
| ecpglib.patch | text/plain | 2.7 KB |
| ecpg-pthread-win32.h | text/x-chdr | 521 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Neil Conway | 2007-03-18 05:31:39 | Re: Code-Cleanup: char* -> const char* |
| Previous Message | Jan Wieck | 2007-03-17 21:53:58 | Re: As proposed the complete changes to pg_trigger and pg_rewrite |