Timezone didn't change.

[macrochel]

Self-hosted supabase via docker-compose

I changed my time zone via ALTER DATABASE postgres SET timezone TO 'Asia/Qyzylorda';
Now, when I run SQL query from supabase GUI:
SHOW TIMEZONE;
Output:
Asia/Qyzylorda

And
SELECT now();
Output
2024-05-01T17:55:41.330Z

BUT when I try to make SQL query directly to postgres
SHOW TIMEZONE;
Output
Asia/Qyzylorda

SELECT now();
Output
2024-05-01T12:55:41.330Z

[encima]

This could be due to the changes. As this is a database setting, often you need to either reload the config or reload the connection.
Does the following work?

• ALTER DATABASE postgres SET timezone TO 'Asia/Qyzylorda';
• SHOW timezone; (should output to original timezone)
• Disconnect and reconnect to the database
• SHOW timezone; (should show 'Asia/Qyzylorda')

If this works then it is expected behaviour. If it does not, let us know what is different!

[macrochel]

Output from SHOW timezone; changes after ALTER DATABASE postgres SET timezone TO 'Asia/Qyzylorda'; instantly without reconnect or the config reload

[encima]

You will need to start a new session for the config to take place. This is not a bug I am afraid

[macrochel]

Starting a new session didn't solve the problem, DB still return time by the old timezone.

[encima]

Sorry to hear that, I am afraid debugging further is hard! I cannot reproduce this on hosted or self-hosted. Potentially someone else might have other ideas!