Ok, it seems the Daylight Savings Time is perfect explanation to me. Thanks y'all, you're the best !
--
Arnaud Becher
Paris - San Francisco
10 rue du Faubourg Poissonnière - 75010 Paris
T. + 33 (0)6 17 15 52 43
http://www.inovia.fr

Paris - San Francisco
10 rue du Faubourg Poissonnière - 75010 Paris
T. + 33 (0)6 17 15 52 43
http://www.inovia.fr



On Wed, May 25, 2016 at 5:01 PM, Kevin Grittner <kgrittn@xxxxxxxxx> wrote:
On Wed, May 25, 2016 at 9:47 AM, Arnaud Inovia Team
<arnaud.becher@xxxxxxxxxxxxxxx> wrote:
> While using "psql", when selecting a column timestamp with
> timezone, I get results with different timezones:
>
> -[ RECORD 6 ]---+-----------------------
> expiration_date | 2015-09-07 00:00:00+02
> -[ RECORD 7 ]---+-----------------------
> expiration_date | 2015-11-27 00:00:00+01
>
> Shouldn't all value be converted to the same timezone ?
Perhaps your local time zone ends Daylight Saving Time between
those dates, so the offset from UTC is different on those dates?
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company