Peculiar time zone handling in a Postgres database
<h2>My environment</h2>

<p>I'm in <strong>Paris, France</strong> (<code>UTC+1</code> or <code>CET</code>).<br>
It's <code>12am</code> (<code>00:00</code>), we're on the <strong>25th of November 2016</strong>.<br>
My <strong>Postgres</strong> database is hosted on <strong>Amazon Web Services</strong> (AWS RDS) in the <code>eu-west-1</code> region.</p>

<h2>The issue</h2>

<p>Querying for the <code>current_date</code> (or <code>current_time</code>) with a specific time zone set seems to deliver results that aren't consistent with... my beliefs.</p>

<p>In particular, querying for the <code>current_date</code> yields a different result when using the <code>CET</code> time zone or the <code>UTC+1</code> one.</p>

<h2>Example</h2>

<pre class="lang-sql prettyprint-override"><code>SET TIME ZONE 'UTC+01';
select current_date, current_time;
</code></pre>

<pre>
+------------+--------------------+
| date       | timetz             |
+------------+--------------------+
| 2016-11-24 | 22:00:01.581552-01 |
+---------------------------------+
</pre>

<p>Nope, that was yesterday -- two hours ago.</p>

<hr>

<pre class="lang-sql prettyprint-override"><code>SET TIME ZONE 'CET';
select current_date, current_time;
</code></pre>

<p>or </p>

<pre class="lang-sql prettyprint-override"><code>SET TIME ZONE 'Europe/Paris';
select current_date, current_time;
</code></pre>

<pre>
+------------+--------------------+
| date       | timetz             |
+------------+--------------------+
| 2016-11-25 | 00:00:01.581552-01 |
+---------------------------------+
</pre>

<p>There's the correct time and date.</p>

<h2>Question</h2>

<p>What's going on there?<br>
Is it too late for me and I mixed up <code>UTC+1</code> and <code>UTC-1</code> or is there something bigger that I'm overlooking?
Does AWS RDS have a role in this?</p>