diff options
| author | Tom Lane | 2016-09-05 00:02:16 +0000 |
|---|---|---|
| committer | Tom Lane | 2016-09-05 00:02:16 +0000 |
| commit | c7f68bea22bf680a4eab4b8b1592b3c90bc634ac (patch) | |
| tree | 9680623577f3fdb232ad9c28baf6379712fe8b5c /src/timezone/README | |
| parent | da6ea70c32bed99ca040a5e04d83c0edd5dfc615 (diff) | |
Add regression test coverage for non-default timezone abbreviation sets.
After further reflection about the mess cleaned up in commit 39b691f25,
I decided the main bit of test coverage that was still missing was to
check that the non-default abbreviation-set files we supply are usable.
Add that.
Back-patch to supported branches, just because it seems like a good
idea to keep this all in sync.
Diffstat (limited to 'src/timezone/README')
| -rw-r--r-- | src/timezone/README | 5 |
1 files changed, 5 insertions, 0 deletions
diff --git a/src/timezone/README b/src/timezone/README index 1df4ce1f69a..f2f80c7176a 100644 --- a/src/timezone/README +++ b/src/timezone/README @@ -34,6 +34,11 @@ in the same commit. Usually, if a known abbreviation has changed meaning, the appropriate fix is to make it refer to a long-form zone name instead of a fixed GMT offset. +The core regression test suite does some simple validation of the zone +data and abbreviations data (notably by checking that the pg_timezone_names +and pg_timezone_abbrevs views don't throw errors). It's worth running it +as a cross-check on proposed updates. + When there has been a new release of Windows (probably including Service Packs), the list of matching timezones need to be updated. Run the script in src/tools/win32tzlist.pl on a Windows machine running this new |