Search Postgresql Archives
Re: bigint out of range
[
Date Prev
][
Date Next
][
Thread Prev
][
Thread Next
][
Date Index
][
Thread Index
]
Subject
: Re: bigint out of range
From
: Tony Shelver <tshelver@xxxxxxxxx>
Date
: Thu, 16 May 2019 18:51:34 +0200
Cc
: "pgsql-general@xxxxxxxxxxxxxxxxxxxx" <pgsql-general@xxxxxxxxxxxxxxxxxxxx>
In-reply-to
: <
BL0PR01MB518741644F902D8F4E447FF99B0A0@BL0PR01MB5187.prod.exchangelabs.com
>
References
: <
BL0PR01MB518741644F902D8F4E447FF99B0A0@BL0PR01MB5187.prod.exchangelabs.com
>
Adding to what David said, I don't see much point of having a bigint status. Usually status attributes are a fixed set of values that can be checked programmatically.
[
Date Prev
][
Date Next
][
Thread Prev
][
Thread Next
][
Date Index
][
Thread Index
]
References
:
bigint out of range
From:
Daulat Ram
Prev by Date:
Permissions for information_schema
Next by Date:
Re: Upgrading 9.1.17 to which version?
Previous by thread:
Re: bigint out of range
Next by thread:
Upgrading 9.1.17 to which version?
Index(es):
Date
Thread
[Index of Archives]
[Postgresql Jobs]
[Postgresql Admin]
[Postgresql Performance]
[Linux Clusters]
[PHP Home]
[PHP on Windows]
[Kernel Newbies]
[PHP Classes]
[PHP Books]
[PHP Databases]
[Postgresql & PHP]
[Yosemite]
