Re: Performance problems with large telemetric datasets on 7.4.2
От | Tom Lane |
---|---|
Тема | Re: Performance problems with large telemetric datasets on 7.4.2 |
Дата | |
Msg-id | 4770.1186180449@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: Performance problems with large telemetric datasets on 7.4.2 (Andrew Kroeger <andrew@sprocks.gotdns.com>) |
Ответы |
Re: Performance problems with large telemetric datasets on 7.4.2
|
Список | pgsql-performance |
Andrew Kroeger <andrew@sprocks.gotdns.com> writes: > With the table definitions you posted, one of the first things I noticed > was that the default value for an integer column was a bigint value. I > did some quick 32-bit math and found that the smallest legal 32-bit > integer value is -2147483648, not -2147483684 (notice the last 2 numbers > are transposed). Oooh, good catch, but 7.4 seems to notice the overflow all right: regression=# create temp table foo(f1 int default -2147483684::bigint); CREATE TABLE regression=# insert into foo default values; ERROR: integer out of range regression=# select version(); version ---------------------------------------------------------------- PostgreSQL 7.4.17 on hppa-hp-hpux10.20, compiled by GCC 2.95.3 (1 row) So I think we can conclude that the OP never actually uses this default. regards, tom lane
В списке pgsql-performance по дате отправления: