Re: Checking for overflow of integer arithmetic

Поиск
Список
Период
Сортировка
От Dave Page
Тема Re: Checking for overflow of integer arithmetic
Дата
Msg-id E7F85A1B5FF8D44C8A1AF6885BC9A0E430688C@ratbert.vale-housing.co.uk
обсуждение исходный текст
Ответ на Checking for overflow of integer arithmetic  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers

> -----Original Message-----
> From: pgsql-hackers-owner@postgresql.org
> [mailto:pgsql-hackers-owner@postgresql.org] On Behalf Of Tom Lane
> Sent: 03 October 2004 20:39
> To: pgsql-hackers@postgresql.org
> Subject: [HACKERS] Checking for overflow of integer arithmetic
>
> 2. For the int2 and int8 operators, should we stick to a
> one-size-fits-all message "integer out of range", or be more
> specific: "smallint out of range" and "bigint out of range"?
> The existing messages are not completely consistent about
> this.  I'm inclined to go with mentioning the specific type
> but I'm not dead set on it.

I vote for being more specific. A little extra info can sometimes ease
debugging problems no matter how trivial it seems.

Regards, Dave.


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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Checking for overflow of integer arithmetic
Следующее
От: Oleg Bartunov
Дата:
Сообщение: slow count() was: tsearch2 poor performance