| From: | hubert depesz lubaczewski <depesz(at)depesz(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Why extract( ... from timestamp ) is not immutable? |
| Date: | 2012-01-25 15:37:27 |
| Message-ID: | 20120125153727.GA23595@depesz.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On Wed, Jan 25, 2012 at 10:35:47AM -0500, Tom Lane wrote:
> hubert depesz lubaczewski <depesz(at)depesz(dot)com> writes:
> > Why aren't the 3rd date_parts the same in both cases? I mean - I see that they
> > are adjusted due to timezone, but why is it happening?
>
> Given a timestamp without time zone, timestamp_part('epoch') assumes
> that it is in session timezone, and rotates it back to UTC so as to
> satisfy the expectation that epoch values start from zero at midnight
> UTC. In short, the calculation you're showing does the zone correction
> an extra time. Don't do that.
ok.
how can I then have immutable epoch for given point in time?
I thought that this is what I will achieve with extract(epoch from now()
at time zone 'UTC') but clearly it doesn't work.
So what options do I have?
Best regards,
depesz
--
The best thing about modern society is how easy it is to avoid contact with it.
http://depesz.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2012-01-25 15:37:44 | Re: Why extract( ... from timestamp ) is not immutable? |
| Previous Message | Tom Lane | 2012-01-25 15:35:47 | Re: Why extract( ... from timestamp ) is not immutable? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2012-01-25 15:37:44 | Re: Why extract( ... from timestamp ) is not immutable? |
| Previous Message | Tom Lane | 2012-01-25 15:35:47 | Re: Why extract( ... from timestamp ) is not immutable? |