I'm taking him at his word as well. He also said in the same interview that "they were looking into it". I guess my point is that for there to a fix in the upcoming patch, either one of two things is true:
1- They found and patched the issue in one day
2- They were already aware and were already working on a fix (which means Pete didn't know about the problem prior to launch or he simply lied)
I'm not suggesting which scenario is true, but one of them is definitely true. Right?
Well, I'm a software tester so I can give an educated guess.
The problem is something that happens on ps3's but not 360's or pcs. This indicates that the other versions had the proper coding and there was an accident/omission made in the PS3 version. Once they found the problem, it could be as easy as a copy/paste or just fixing the code to match the intended results that the same code has in the other versions.
I have ultimately figured out the problem (http://www.gamesas.com/index.php?/topic/1284052-i-can-verify-the-problem-and-a-temporary-solution/), through testing it on my own machine. It seems to be a memory dump/refresh issue which could be simple.
The thing is, their testers and developers are very smart. Even if it was a complicated fix, they have enough resources to make a one-day turn around if pressed.
Additionally, they may have already been working on a fix without realizing the full extent of the problem. I've had times where I found a problem in our software (the company I work for) and have said the problem only to have the dev team say, "So what?" I then have to explain the ramifications and they their faces drop and they get right to work because the software would break.
So there you have it, a glimpse into testing/developing.
@Zidane: They may not have been working on the ps3 version specifically for those three years. Also, this error could have been introduced at any point of production before code lockdown. For all we know, their last entry caused the problem and it was just missed that one time.