Re: @(#) Mordred Labs advisory 0x0001: Buffer overflow in
От | Rod Taylor |
---|---|
Тема | Re: @(#) Mordred Labs advisory 0x0001: Buffer overflow in |
Дата | |
Msg-id | 1029815887.86008.26.camel@jester обсуждение исходный текст |
Ответ на | Re: @(#) Mordred Labs advisory 0x0001: Buffer overflow in ("Christopher Kings-Lynne" <chriskl@familyhealth.com.au>) |
Ответы |
Re: @(#) Mordred Labs advisory 0x0001: Buffer overflow in
Re: @(#) Mordred Labs advisory 0x0001: Buffer overflow in |
Список | pgsql-hackers |
On Mon, 2002-08-19 at 23:50, Christopher Kings-Lynne wrote: > > > I'd like to see something done about this fairly soon, but it's not > > > happening for 7.3 ... > > > > Hang on, you seem to be suggesting we release a major new upgrade, with > > major new functionality, knowing it contains a way to trivially crash > > the backend. > > > > Err.. hang on. What happened to our reputation for quality and > > releasing "when it's ready"? > > > > Since when were we Microsoft-ized? > > I personally agree with Justin that it should be fixed for 7.3 (just imagine > all those people selling colo postgres services). There should be a 7.2.2 > as well that fixes the date parser problem. Has anyone actually considered the time required to make the appropriate fix (clean up use of OPAQUE)? I don't think this bug is worthy of pushing the 7.3 release out a few weeks. The simple fix is to drop the money type entirely as it serves few purposes -- but there are some who use it.
В списке pgsql-hackers по дате отправления: