From: | Nicolai Tufar <ntufar(at)gmail(dot)com> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, Magnus Hagander <mha(at)sollentuna(dot)net>, pgsql-hackers(at)postgresql(dot)org, pgsql-hackers-win32(at)postgresql(dot)org, pgsql-patches(at)postgresql(dot)org, devrim(at)gunduz(dot)org |
Subject: | Re: [pgsql-hackers-win32] Repleacement for src/port/snprintf.c |
Date: | 2005-02-15 14:29:27 |
Message-ID: | d80929390502150629558be007@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-hackers-win32 pgsql-patches |
On Sun, 13 Feb 2005 19:06:34 -0500 (EST), Bruce Momjian
<pgman(at)candle(dot)pha(dot)pa(dot)us> wrote:
> Anyway, this is too large to put into 8.0, but I am attaching a patch
> for 8.1 that has the proper configure tests to check if the C library
> supports this behavior. If it does not, the build will use our
> port/snprintf.c.
> One problem with that is that our snprintf.c is not thread-safe. Seems
> the increases use of it will require us to fix this soon. I have added
> to TODO:
>
> * Make src/port/snprintf.c thread-safe
Okay, I am applying your patch to CVS HEAD and
getting hands on making snprintf.c thread-safe. I will
submit a roll up pathch in a day or two.
Regards,
Nicolai
From | Date | Subject | |
---|---|---|---|
Next Message | E.Rodichev | 2005-02-15 15:59:10 | |
Previous Message | Zeugswetter Andreas DAZ SD | 2005-02-15 14:27:28 | Re: enforcing a plan (in brief) |
From | Date | Subject | |
---|---|---|---|
Next Message | Jamie Deppeler | 2005-02-18 04:00:16 | replication for win32 |
Previous Message | Bruce Momjian | 2005-02-14 00:06:34 | Re: [pgsql-hackers-win32] Repleacement for src/port/snprintf.c |
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2005-02-15 14:54:43 | Re: Shared dependency patch |
Previous Message | Tom Lane | 2005-02-15 05:47:34 | Re: Which release cycle are we in? |