storj/satellite/satellitedb/dbx
Bill Thorp e99e675fb1 satellite/satellitedb: use time zones with all timestamps
The migration was broken into one migration per table to reduce table locking and reduce the
chances of failure due to SQL timeouts.

Of the 14 fields that lacked time zones, only the 3 named 'interval_start` seemed to have non-UTC data in them.
These fields are fixed in the migration by removing the +00 and adding  AT TIME ZONE current_setting('TIMEZONE')
Field with good data are migrated by adding AT TIME ZONE 'UTC'

Note that postgres's timezone() is different than cockroach's timezone() so AT TIME ZONE is used.

https://storjlabs.atlassian.net/browse/SM-104

Change-Id: I410f2f1d7c11b143f17844347f37e6f4b1e70fce
2020-03-05 21:11:25 +00:00
..
templates satellite/satellitedb/dbx: monitor the database calls 2019-12-18 21:57:36 +00:00
gen.go all: use monkit v3 2020-02-05 23:53:17 +00:00
gen.sh satellite/satellitedb/dbx: Remove bashism from gen.sh 2020-01-23 17:09:07 -05:00
satellitedb.dbx satellite/satellitedb: use time zones with all timestamps 2020-03-05 21:11:25 +00:00
satellitedb.dbx.cockroach.sql satellite/satellitedb: use time zones with all timestamps 2020-03-05 21:11:25 +00:00
satellitedb.dbx.go satellite/satellitedb: use time zones with all timestamps 2020-03-05 21:11:25 +00:00
satellitedb.dbx.postgres.sql satellite/satellitedb: use time zones with all timestamps 2020-03-05 21:11:25 +00:00