Re: [BUGS] BUG #9652: inet types don't support min/max

Поиск
Список
Период
Сортировка
От Asif Naeem
Тема Re: [BUGS] BUG #9652: inet types don't support min/max
Дата
Msg-id CAEB4t-PznBeb2kPhUtUAMGrLHmxjWAkf9sm4EBEtN-n44mAX=Q@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [BUGS] BUG #9652: inet types don't support min/max  (Haribabu Kommi <kommi.haribabu@gmail.com>)
Ответы Re: [BUGS] BUG #9652: inet types don't support min/max
Список pgsql-hackers
Thank you Haribabu. Please see my comments inlined below i.e.

On Sun, Jul 27, 2014 at 11:42 AM, Haribabu Kommi <kommi.haribabu@gmail.com> wrote:
On Thu, Jul 24, 2014 at 5:59 PM, Asif Naeem <anaeem.it@gmail.com> wrote:
> Sorry for being late. Thank you for sharing updated patch, sgml changes
> seems not working i.e.
>
>> postgres=# select max('192.168.1.5', '192.168.1.4');
>> ERROR:  function max(unknown, unknown) does not exist
>> LINE 1: select max('192.168.1.5', '192.168.1.4');
>>
>>                ^
>> HINT:  No function matches the given name and argument types. You might
>> need to add explicit type casts.
>> postgres=# select min('192.168.1.5', '192.168.1.4');
>> ERROR:  function min(unknown, unknown) does not exist
>> LINE 1: select min('192.168.1.5', '192.168.1.4');
>>
>>                ^
>> HINT:  No function matches the given name and argument types. You might
>> need to add explicit type casts.

I didn't get your point. I tested the patch, the sgml changes are working fine.

Sorry for not being clear, above mentioned test is related to following doc (sgml) changes that seems not working as described i.e.

Table 9-35. cidr and inet Functions

FunctionReturn TypeDescriptionExampleResult





max(inetinet)inetlarger of two inet typesmax('192.168.1.5', '192.168.1.4')192.168.1.5
min(inetinet)inetsmaller of two inet typesmin('192.168.1.5', '192.168.1.4')192.168.1.4






Can you please elaborate these sgml change ?
 
> I would suggest the following or similar changes e.g.
>
>> doc/src/sgml/func.sgml
>>         </indexterm>
>>         <function>max(<replaceable
>> class="parameter">expression</replaceable>)</function>
>>        </entry>
>> -      <entry>any array, numeric, string, or date/time type</entry>
>> +      <entry>any inet, array, numeric, string, or date/time type</entry>
>>        <entry>same as argument type</entry>
>>        <entry>
>>         maximum value of <replaceable
>> @@ -12204,7 +12228,7 @@ NULL baz</literallayout>(3 rows)</entry>
>>         </indexterm>
>>         <function>min(<replaceable
>> class="parameter">expression</replaceable>)</function>
>>        </entry>
>> -      <entry>any array, numeric, string, or date/time type</entry>
>> +      <entry>any inet, array, numeric, string, or date/time type</entry>
>>        <entry>same as argument type</entry>
>>        <entry>
>>         minimum value of <replaceable

Thanks for reviewing the patch.
I missed the above change. Corrected the same in the attached patch.

Regards,
Hari Babu
Fujitsu Australia

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Gavin Flower
Дата:
Сообщение: Re: Proposed changing the definition of decade for date_trunc and extract
Следующее
От: Dilip kumar
Дата:
Сообщение: Re: TODO : Allow parallel cores to be used by vacuumdb [ WIP ]