docker-library / docker-library/postgres

Obsolete time zones not recognized anymore

Open
#1,355 10 comments 11 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Shell
Stars
2.5k
Forks
1.2k
PR merge metrics
No merged PRs in 30d

Description

After the debian trixie update yesterday it looks like that my django app tests started to error with:

psycopg.errors.InvalidParameterValue: time zone "America/Buenos_Aires" not recognized
psycopg.errors.InvalidParameterValue: time zone "America/Indianapolis" not recognized
psycopg.errors.InvalidParameterValue: time zone "Asia/Ashkhabad" not recognized
psycopg.errors.InvalidParameterValue: time zone "Asia/Chungking" not recognized
psycopg.errors.InvalidParameterValue: time zone "Asia/Macao" not recognized
psycopg.errors.InvalidParameterValue: time zone "Asia/Thimbu" not recognized
psycopg.errors.InvalidParameterValue: time zone "Australia/NSW" not recognized
psycopg.errors.InvalidParameterValue: time zone "Australia/South" not recognized
psycopg.errors.InvalidParameterValue: time zone "Australia/West" not recognized
psycopg.errors.InvalidParameterValue: time zone "Brazil/Acre" not recognized
psycopg.errors.InvalidParameterValue: time zone "Canada/Atlantic" not recognized
psycopg.errors.InvalidParameterValue: time zone "Chile/EasterIsland" not recognized
psycopg.errors.InvalidParameterValue: time zone "Europe/Uzhgorod" not recognized
psycopg.errors.InvalidParameterValue: time zone "Iran" not recognized
psycopg.errors.InvalidParameterValue: time zone "NZ" not recognized
psycopg.errors.InvalidParameterValue: time zone "Pacific/Truk" not recognized
psycopg.errors.InvalidParameterValue: time zone "Singapore" not recognized
psycopg.errors.InvalidParameterValue: time zone "US/Michigan" not recognized

These are old obsolete time zone names that worked until the debian new trixie base image upgraded tzdata.

Just opened this issue as it was a little surprising breaking change as the postgres version didn't change.

I'm also fine if this is just noted as expected side effect.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the PostgreSQL Docker image's Debian trixie base-image and tzdata upgrade, then verify how the listed obsolete time-zone names are handled by PostgreSQL. Determine whether compatibility should be restored or the breaking change documented; done means the expected behavior and user-facing resolution are established.

Written by the indexing model from the issue text.

Assessment

Tech stack
debian, docker, postgresql
Domain
databases, infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.