Re: pgsql: Trivial dead code removal: in makeObjectName(), name1 must be
От | Tom Lane |
---|---|
Тема | Re: pgsql: Trivial dead code removal: in makeObjectName(), name1 must be |
Дата | |
Msg-id | 19364.1119321504@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | pgsql: Trivial dead code removal: in makeObjectName(), name1 must be (neilc@svr1.postgresql.org (Neil Conway)) |
Ответы |
Re: pgsql: Trivial dead code removal: in makeObjectName(),
|
Список | pgsql-committers |
neilc@svr1.postgresql.org (Neil Conway) writes: > Trivial dead code removal: in makeObjectName(), name1 must be non-NULL > (due to the preceding strlen(), for example), so we needn't recheck this > before invoking pg_mbcliplen(). I don't like either this change or the tab-complete one: this seems to me to reduce readability, as well as robustness in the face of future changes, in order to save nothing at all worth mentioning. If these were performance-critical paths it might be worth doing, but they are not. What's more, given a reasonably-intelligent optimizing compiler the same deductions would be made at compile time, and so it's a fair bet that you have bought not roughly but exactly zero in return for making the code more fragile and less readable. The schemacmds.c change seems OK since it's not introducing any obvious path for future breakage. regards, tom lane
В списке pgsql-committers по дате отправления: