From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | Neil Conway <neilc(at)samurai(dot)com>, PostgreSQL Patches <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: (yet) more buffer paranoia |
Date: | 2002-08-24 04:52:55 |
Message-ID: | 25619.1030164775@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> writes:
> I guess the question is where there are tons more. If not, I think it
> would be wise to just clean it up so any future uses will look out of
> place.
Should I point out that Neil already managed to break the regression
tests on the eve of an emergency patch-release with a completely
unnecessary snprintf-ization of show_datestyle?
There *are* risks in changing working code, and while those risks may be
small, I don't see the point of taking them in places where the benefit
is provably zero. If it's not obvious that a sprintf or similar can't
overflow its buffer, then by all means make it snprintf instead. But
I don't hold with the idea that sprintf is ipso facto bad.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Neil Conway | 2002-08-24 05:04:12 | Re: (yet) more buffer paranoia |
Previous Message | Bruce Momjian | 2002-08-24 04:39:26 | Re: (yet) more buffer paranoia |