Re: GinPageIs* don't actually return a boolean
От | Yury Zhuravlev |
---|---|
Тема | Re: GinPageIs* don't actually return a boolean |
Дата | |
Msg-id | c3f0eca7-9303-4a7d-9150-257dcc5d520d@postgrespro.ru обсуждение исходный текст |
Ответ на | Re: GinPageIs* don't actually return a boolean (Robert Haas <robertmhaas@gmail.com>) |
Ответы |
Re: GinPageIs* don't actually return a boolean
Re: GinPageIs* don't actually return a boolean |
Список | pgsql-hackers |
Robert Haas wrote: > On Wed, Mar 2, 2016 at 9:48 PM, Peter Eisentraut <peter_e@gmx.net> wrote: >> On 2/11/16 9:30 PM, Michael Paquier wrote: ... > > We need to decide what to do about this. I disagree with Peter: I > think that regardless of stdbool, what we've got right now is sloppy > coding - bad style if nothing else. Furthermore, I think that while C > lets you use any non-zero value to represent true, our bool type is > supposed to contain only one of those two values. Therefore, I think > we should commit the full patch, back-patch it as far as somebody has > the energy for, and move on. But regardless, this patch can't keep > sitting in the CommitFest - we either have to take it or reject it, > and soon. > I know that we are trying to do the right thing. But right now there is an error only in ginStepRight. Maybe now the fix this place, and we will think about "bool" then? The patch is attached (small and simple). Thanks. -- Yury Zhuravlev Postgres Professional: http://www.postgrespro.com The Russian Postgres Company
Вложения
В списке pgsql-hackers по дате отправления: