title: Time zone for PostgreSQL by accessing through client and DBeaver
body: <p>I have one table in the postgresql database (engine verion 10.11) with a column called resettime which has the datatype as timestamptz. The default timezone for the database is &quot;Australia/Sydney&quot;.</p>
  <p>The column resettime has the default value as timezone('UTC'::text, now()).</p>
  <p>I ran the following command to set this column in DBEaver.</p>
  <p><code>update mytable set resettime = timezone('UTC', now()) + interval '1 hour' where id = 1;</code></p>
  <p>The current UTC time is <code>11:47</code>, and the corresponding AEST time is <code>21:47</code></p>
  <p>After running the above statement, I tried to get the resettime by the following statement in DBEaver.</p>
  <p><code>select resettime from mytable where id=1</code></p>
  <p>From this statement, I got <code>2020-09-14 12:47:25</code>.</p>
  <p>Then, I run the following command in DBEaver.</p>
  <p><code>update mytable set resettime = resettime + interval '1 hour' where resettime &lt; timezone('UTC', now());</code></p>
  <p>After run this command, I check the resettime for the record with id=1, I found the resettime was kept as my expectation. It is normal.</p>
  <p>However, when I ran the same update statement in my scala application, it updated the resettime as <code>2020-09-14 13:47:25</code>. I have a feeling that resettime is still regarded as AEST time if I accessed it through my scala application. I do not want to change the default timezone settings to UTC.</p>
  <p>How should I ensure my scala application also get the same behavior as my access through DBEaver? In the above example, I hope the resettime is not changed by my scala application to run the same update statement. Thanks!</p>