Re: [PERFORM] typoed column name, but postgres didn't grump
От | Tom Lane |
---|---|
Тема | Re: [PERFORM] typoed column name, but postgres didn't grump |
Дата | |
Msg-id | 9887.1288389232@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: [PERFORM] typoed column name, but postgres didn't grump (Robert Haas <robertmhaas@gmail.com>) |
Ответы |
Re: [PERFORM] typoed column name, but postgres didn't grump
|
Список | pgsql-bugs |
Robert Haas <robertmhaas@gmail.com> writes: > Yeah, I think we're going to have to live with it, at least for 8.4. One could make an argument that 9.0 is new enoughwe could get away with a small behavior change to avoid a large amount of user confusion. But that may be a self-servingargument based on wanting to tamp down the bug reports rather than a wisely considered policy decision... soI'm not sure I quite buy it. Well, tamping down the bug reports is good from the users' point of view too. The argument for not changing it in the back branches is that there might be someone depending on the 8.4/9.0 behavior. However, that seems moderately unlikely. Also, if we wait, that just increases the chances that someone will come to depend on it, and then have a problem when they migrate to 9.1. I think the "risk of breakage" argument has a lot more force when considering long-standing behaviors than things we just recently introduced. regards, tom lane
В списке pgsql-bugs по дате отправления: