Time zones and AT TIME ZONE in PostgreSQL - Practice Problems & Coding Challenges

Challenge - 5 Problems

❓ query_result

intermediate

Convert timestamp to a different time zone

Given the timestamp '2024-06-01 15:00:00' in UTC, what is the result of converting it to 'America/New_York' using AT TIME ZONE in PostgreSQL?

PostgreSQL

SELECT '2024-06-01 15:00:00'::timestamp AT TIME ZONE 'UTC' AT TIME ZONE 'America/New_York';

A 2024-06-01 15:00:00

B 2024-06-01 20:00:00

C 2024-06-01 10:00:00

D 2024-06-01 11:00:00

💡 Hint

Remember that New York is UTC-4 during daylight saving time in June.

The timestamp is first treated as UTC, then converted to America/New_York time zone, which is UTC-4 in June, so 15:00 UTC becomes 11:00 local time.

❓ query_result

intermediate

Effect of AT TIME ZONE on timestamp with time zone

What is the output of this query? SELECT '2024-06-01 15:00:00+00'::timestamptz AT TIME ZONE 'America/Los_Angeles';

PostgreSQL

SELECT '2024-06-01 15:00:00+00'::timestamptz AT TIME ZONE 'America/Los_Angeles';

A 2024-06-01 08:00:00

B 2024-06-01 22:00:00

C 2024-06-01 15:00:00

D 2024-06-01 07:00:00

💡 Hint

Los Angeles is UTC-7 during daylight saving time in June.

The timestamptz is converted to the local time in America/Los_Angeles by subtracting 7 hours from UTC, so 15:00 UTC becomes 08:00 local time.

📝 Syntax

advanced

Identify the syntax error in time zone conversion

Which option contains a syntax error when converting timestamp to a time zone in PostgreSQL?

A SELECT '2024-06-01 15:00:00'::timestamp AT TIME ZONE 'UTC';

B SELECT '2024-06-01 15:00:00'::timestamp AT TIMEZONE 'UTC';

C SELECT '2024-06-01 15:00:00'::timestamp AT TIME ZONE 'America/New_York';

D SELECT '2024-06-01 15:00:00+00'::timestamptz AT TIME ZONE 'UTC';

💡 Hint

Check the exact spelling and spacing of the AT TIME ZONE clause.

The keyword must be exactly 'AT TIME ZONE' with spaces. 'AT TIMEZONE' without space is invalid syntax.

❓ optimization

advanced

Optimizing queries with multiple time zone conversions

Which query is the most efficient way to convert a UTC timestamp to 'Europe/Paris' local time and then back to UTC in PostgreSQL?

A SELECT (ts AT TIME ZONE 'UTC') AT TIME ZONE 'Europe/Paris' AT TIME ZONE 'UTC' FROM (SELECT '2024-06-01 12:00:00'::timestamp AS ts) sub;

B SELECT ts AT TIME ZONE 'UTC' AT TIME ZONE 'Europe/Paris' AT TIME ZONE 'UTC' FROM (SELECT '2024-06-01 12:00:00'::timestamp AS ts) sub;

C SELECT (ts AT TIME ZONE 'Europe/Paris') AT TIME ZONE 'UTC' FROM (SELECT '2024-06-01 12:00:00+00'::timestamptz AS ts) sub;

D SELECT ts AT TIME ZONE 'Europe/Paris' FROM (SELECT '2024-06-01 12:00:00+00'::timestamptz AS ts) sub;

💡 Hint

Consider the data types and the order of conversions to avoid redundant operations.

Option C converts timestamptz to Europe/Paris local time and then back to UTC efficiently. Other options have redundant or incorrect conversions.

🧠 Conceptual

expert

Understanding AT TIME ZONE behavior with timestamp and timestamptz

Which statement correctly describes the behavior of AT TIME ZONE in PostgreSQL when applied to timestamp without time zone and timestamp with time zone types?

A For timestamp without time zone, AT TIME ZONE treats the timestamp as local time in the given zone and converts it to UTC; for timestamptz, it converts UTC to the given time zone local time.

B For timestamp without time zone, AT TIME ZONE converts the timestamp to UTC ignoring the given zone; for timestamptz, it converts UTC to local time in the given zone.

C For timestamp without time zone, AT TIME ZONE converts the timestamp to the given time zone local time; for timestamptz, it converts local time to UTC.

D For both timestamp and timestamptz, AT TIME ZONE converts the timestamp to UTC regardless of the given zone.

💡 Hint

Think about how PostgreSQL treats timestamp types differently with AT TIME ZONE.

AT TIME ZONE converts timestamp without time zone by assuming it is in the given zone and returns timestamptz in UTC. For timestamptz, it converts UTC to local time in the given zone returning timestamp without time zone.

Practice

1. What does the AT TIME ZONE clause do in PostgreSQL?

easy

A. It converts a timestamp from one time zone to another.

B. It changes the system time zone permanently.

C. It formats the timestamp as a string.

D. It deletes time zone information from a timestamp.

Solution

1. Step 1: Understand the purpose of AT TIME ZONE

   This clause is used to convert timestamps between different time zones.

2. Step 2: Compare options

   Only It converts a timestamp from one time zone to another. correctly describes this conversion. Other options describe unrelated actions.

3. Final Answer:

   It converts a timestamp from one time zone to another. -> Option A

4. Quick Check:

   AT TIME ZONE converts time zones [OK]

Hint: Remember: AT TIME ZONE changes time zones, not system settings [OK]

Common Mistakes:

• Thinking it changes system time zone permanently
• Confusing it with formatting functions
• Assuming it removes time zone info

2. Which of the following is the correct syntax to convert a timestamp to 'America/New_York' time zone in PostgreSQL?

easy

A. SELECT timestamp_column AT TIMEZONE 'America/New_York';

B. SELECT timestamp_column AT TIME ZONE 'America/New_York';

C. SELECT timestamp_column AT TIMEZONE America/New_York;

D. SELECT timestamp_column AT TIME ZONE America/New_York;

Solution

1. Step 1: Recall correct syntax for AT TIME ZONE

   The correct syntax uses two words: AT TIME ZONE followed by the time zone in single quotes.

2. Step 2: Check each option

   Only SELECT timestamp_column AT TIME ZONE 'America/New_York'; matches the correct syntax exactly. The others either use AT TIMEZONE as one word (incorrect spelling) or miss quotes around the time zone name.

3. Final Answer:

   SELECT timestamp_column AT TIME ZONE 'America/New_York'; -> Option B

4. Quick Check:

   Use AT TIME ZONE 'zone' with quotes [OK]

Hint: Use two words: AT TIME ZONE with quotes around zone [OK]

Common Mistakes:

• Writing AT TIMEZONE as one word
• Omitting quotes around time zone
• Using incorrect keyword order

3. Given the query:

SELECT '2024-06-01 12:00:00'::timestamp AT TIME ZONE 'UTC' AT TIME ZONE 'America/Los_Angeles';

What is the output timestamp?

medium

A. 2024-06-01 20:00:00

B. 2024-06-01 04:00:00

C. 2024-06-01 05:00:00

D. 2024-06-01 12:00:00

Solution

1. Step 1: Understand the query steps

   The first AT TIME ZONE 'UTC' converts the timestamp without time zone to UTC timestamp with time zone. The second AT TIME ZONE 'America/Los_Angeles' converts that UTC time to Los Angeles local time.

2. Step 2: Calculate time difference

   On June 1, Los Angeles is on PDT (UTC-7). So 12:00 UTC minus 7 hours is 05:00 local time. But since the query applies AT TIME ZONE twice, the final output is a timestamp without time zone in Los Angeles time, which is 05:00.

3. Final Answer:

   2024-06-01 05:00:00 -> Option C

4. Quick Check:

   UTC 12:00 minus 7 hours = 05:00 [OK]

Hint: Remember LA is UTC-7 in June; subtract 7 hours [OK]

Common Mistakes:

• Confusing the order of AT TIME ZONE conversions
• Ignoring daylight saving time offset
• Assuming output is in UTC

4. Identify the error in this query:

SELECT '2024-06-01 12:00:00'::timestamp AT TIMEZONE 'Europe/London';

medium

A. The timestamp literal is missing time zone info.

B. The query is correct and will run without error.

C. The time zone name is invalid.

D. The keyword should be AT TIME ZONE with a space.

Solution

1. Step 1: Check the syntax of AT TIME ZONE

   The query uses AT TIMEZONE as one word, which is incorrect syntax in PostgreSQL.

2. Step 2: Verify other parts

   The timestamp literal is valid, and 'Europe/London' is a valid time zone name. So no error there.

3. Final Answer:

   The keyword should be AT TIME ZONE with a space. -> Option D

4. Quick Check:

   Use two words: AT TIME ZONE [OK]

Hint: Always write AT TIME ZONE as two words [OK]

Common Mistakes:

• Writing AT TIMEZONE as one word
• Assuming timestamp needs time zone info
• Thinking time zone name is invalid

5. You have a timestamp with time zone column created_at stored in UTC. You want to display it as local time in 'Asia/Tokyo' but keep it as timestamp without time zone. Which query correctly does this?

hard

A. SELECT created_at AT TIME ZONE 'Asia/Tokyo' FROM orders;

B. SELECT created_at::timestamp AT TIME ZONE 'Asia/Tokyo' FROM orders;

C. SELECT (created_at AT TIME ZONE 'UTC') AT TIME ZONE 'Asia/Tokyo' FROM orders;

D. SELECT created_at AT TIME ZONE 'UTC' AT TIME ZONE 'Asia/Tokyo' FROM orders;

Solution

1. Step 1: Understand data type and conversion

   created_at is timestamp with time zone in UTC. Applying AT TIME ZONE 'Asia/Tokyo' converts it to timestamp without time zone in Tokyo local time.

2. Step 2: Analyze options

   SELECT created_at AT TIME ZONE 'Asia/Tokyo' FROM orders; correctly applies AT TIME ZONE 'Asia/Tokyo' to convert UTC timestamptz to local timestamp. SELECT created_at::timestamp AT TIME ZONE 'Asia/Tokyo' FROM orders; casts to timestamp first, losing time zone info before conversion, causing wrong result. The options that apply AT TIME ZONE 'UTC' first perform extra and incorrect conversions.

3. Final Answer:

   SELECT created_at AT TIME ZONE 'Asia/Tokyo' FROM orders; -> Option A

4. Quick Check:

   timestamptz AT TIME ZONE zone = local timestamp [OK]

Hint: Apply AT TIME ZONE directly on timestamptz to get local timestamp [OK]

Common Mistakes:

• Casting timestamptz to timestamp before conversion
• Applying multiple AT TIME ZONE conversions unnecessarily
• Confusing timestamp with and without time zone