You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In our production instance, the id field in waveforms_continuoustrace table is currently at ~200e6. For postgres type integer that is ~10% of the maximum value possible (~2.1e9). I assume that problems might/will arise if we ever hit the maximum value? So in the future it might be a good idea to use bigint for that field instead (it seems that postgres does not have unsigned integer types, unfortunately?).
The text was updated successfully, but these errors were encountered:
In our production instance, the
id
field inwaveforms_continuoustrace
table is currently at ~200e6. For postgres typeinteger
that is ~10% of the maximum value possible (~2.1e9). I assume that problems might/will arise if we ever hit the maximum value? So in the future it might be a good idea to usebigint
for that field instead (it seems that postgres does not have unsigned integer types, unfortunately?).The text was updated successfully, but these errors were encountered: