> Tatsuo Ishii <[EMAIL PROTECTED]> writes:
> > Thanks. I have confirmed that at least following reports are
> > correct. Will fix them.
>
> I already committed fixes in HEAD and 7.3 branch.
Thanks.
> I wanted to ask you if this might explain some of the odd reports we've
> gotten about conversio
Tatsuo Ishii <[EMAIL PROTECTED]> writes:
> Thanks. I have confirmed that at least following reports are
> correct. Will fix them.
I already committed fixes in HEAD and 7.3 branch.
I wanted to ask you if this might explain some of the odd reports we've
gotten about conversion problems? I can't re
I think it's 'coz the only assignment to "plpgsql_nDatums" the checker
could find is on line 176, without realizing plpgsql_nDatums is actually a
global variable and could be changed anywhere... We'll rule out cases like
this in the future. Thanks for letting us know. --yichen
On Tue, 28 Jan 2003,
Both are flagged though--the other one's 85 lines down in the bug report..
;) I probably should've sorted the list by location to minimize confusion.
Thanks for the feedback!
-Yichen
On Tue, 28 Jan 2003, Tom Lane wrote:
> This looks like great stuff --- I haven't read through all of them, but
"Yichen Xie" <[EMAIL PROTECTED]> writes:
> We are a group of Stanford researchers, and we've recently developed a
> tool that detects potential out-of-bounds array accesses and buffer
> overruns. Here are 9 potential bugs we've found on postgresql 7.3.1.
Here's a status report:
> [BUG] MAX_TIME_P
> We are a group of Stanford researchers, and we've recently developed a
> tool that detects potential out-of-bounds array accesses and buffer
> overruns. Here are 9 potential bugs we've found on postgresql 7.3.1.
> We've been checking linux for a few years, and we're interested in
> expanding to o
Yichen Xie <[EMAIL PROTECTED]> writes:
> Both are flagged though--the other one's 85 lines down in the bug report..
> ;) I probably should've sorted the list by location to minimize confusion.
That's okay, I probably should've read the whole mail before commenting ;-)
I'm confused by the entry
"Yichen Xie" <[EMAIL PROTECTED]> writes:
> We are a group of Stanford researchers, and we've recently developed a
> tool that detects potential out-of-bounds array accesses and buffer
> overruns. Here are 9 potential bugs we've found on postgresql 7.3.1.
> We've been checking linux for a few years,
