On Mon, 17 Jan 2005 14:54:44 -0500, Tom Lane <[EMAIL PROTECTED]> wrote:
> Also, it looks like src/port/snprintf.c is not %n$ capable either.
> I'm not sure which platforms that affects.
>
> A possible route to a solution is to upgrade snprintf.c and then use
> it on platforms that don't have this
>> I don't think we'll hold up release to fix this, but the affected
>> translators may want to think about whether they can avoid
>the problem
>> or not.
>
>Also, it looks like src/port/snprintf.c is not %n$ capable either.
>I'm not sure which platforms that affects.
>
>A possible route to a solu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
On Mon, 17 Jan 2005, Tom Lane wrote:
I don't think we'll hold up release to fix this,
:-) It seems nothing seems to stop you from holding up this release
anymore: Neither ARC problem nor this one :)
Regards,
- --
Devrim GUNDUZ
devrim~gunduz.org,
I wrote:
> I don't think we'll hold up release to fix this, but the affected
> translators may want to think about whether they can avoid the problem
> or not.
Also, it looks like src/port/snprintf.c is not %n$ capable either.
I'm not sure which platforms that affects.
A possible route to a solut
Nicolai Tufar <[EMAIL PROTECTED]> writes:
> Sorry for such a late submission.
> I just downloaded the latest postgresql-8.0.0-rc5-3.zip installer
> for windows and it appears that Windows' printf() does not
> support placeholder replacement as described in
> http://developer.postgresql.org/docs/pos
