Re: BUG #18884: The CURRENT_TIMESTAMP value being returned in UTC-2.

This issue is not in your Postgres Driver but in Postgres Server.

On Tue, 8 Apr 2025 at 15:57, PG Bug reporting form <noreply(at)postgresql(dot)org>
wrote:

> The following bug has been logged on the website:
>
> Bug reference: 18884
> Logged by: Test Test
> Email address: testtest12423(at)gmail(dot)com
> PostgreSQL version: 17.2
> Operating system: Windows
> Description:
>
> I hope you are doing well.
>
> When using your postgresql driver, i faced an incosistence behavior.
>
> Query: boolean ret = stat.execute("SELECT CURRENT_TIMESTAMP AS
> CURRENT_TIMESTAMP, " +
> "CAST(CURRENT_TIMESTAMP as text) AS
> CURRENT_TIMESTAMP_TEXT,"
> +
> " EXTRACT(HOUR FROM CURRENT_TIMESTAMP) AS HOUR FROM
> \"Test_Table\"");
>
> CURRENT_TIMESTAMP => is displayed in my TimeZone
> CURRENT_TIMESTAMP_TET => is displayed in UTC -02
> HOUR => the hour value from UTC-2.
>
> Server Timezone information:
> https://monosnap.com/file/rf9QeIGVj9C0lssQa5TRBHYsqISAew
>
> Java Code: https://monosnap.com/file/4cJglQhT5ok9gTdyakxEmt11VlZFUU
>
> However adding the following property in connection URL, changes the
> output.
> String url = "jdbc:postgresql://127.0.0.1:5432/postgres?loggerLevel=INFO";
>
> Please have a look at the following picture:
> https://monosnap.com/file/dWqXiUjggsl6Db29bDr6Q5YAQcQz57
>
> Using another driver, i found from decoding TCP packets that server is
> returning CURRENT_TIMESTAMP in UTC -2.
>
> As mentioned server IS in UTC + 2 and not -2.
>
> Can you please let me know your thoughts?
>
>